Is Clearing Browser Cache a Common Kinetic Issue for Your Users?

Kinetic ERP
, , , ,
1

EpicCare Support told me browser-cache issues are not widely reported, but we regularly see blank screens, missing controls, applications not loading, and MES issues that are resolved by clearing cache or restarting the browser.

I suspect the issue is underreported because users, supervisors, and IT teams have learned to fix it themselves.

Is clearing browser cache a recurring issue in your Kinetic environment? Please share how often it happens and whether it is typically connected to upgrades or hotfixes.

I also submitted Idea KIN-I-7825: Eliminate the Need to Clear Browser Cache After Kinetic Updates.

2

Yes.

3

Yes.

So far, I’d guess it is connected w/upgrades but hard to say if hotfixes alone would cause it.

Because it manifests so erratically and in different screens, I couldn’t even guess at frequency.

4

It’s so common I wore my, “This is my yes, I cleared the cache shirt” t-shirt to insights 2 years ago. I doubt there is any way to eliminate this. Just teach your users how to do it and move on.

5

We use plenty of other web applications that update constantly, and we don’t have to train users to clear cache. Those applications manage version changes and stale resources automatically. Epicor can do the same.

6

are you new GIF

7

Clearing cache was a first step in Classic so it’s no surprise it’s still true in Kinetic UI.

8

All the time.

9

Was worried it was just us haha

10

yes, we see these issues. Mostly after an upgrade, but occasionally random times

11

Same…telling users to clear cache has become the standard “step 1” in trying to diagnose a Kinetic issue.

Not unlike…

image
image480×345 44.1 KB

12

Multiple users, daily, need to clear their browser cache. If I’m helping remotely, I’ve just been opening Dev Tools → Network Tab and checking the “Disable cache” checkbox, then do a refresh. This seems to force a reload of -all- content that even Ctrl-F5 misses, and avoids blowing away the user’s browser cache for other sites.

We’ve also had issues with users who run both MES and the full client in the same browser. This seems to trigger SSO (Azure) authentication issues. Multiple users get into login loops after their MES/full client session idles out. Generally this requires a full clear and browser close to resolve. It’s pretty messy.

13

We’ve also had issues with users who run both MES and the full client in the same browser.

I’ve recently learned that users in this situation should use Office MES instead of Shop Floor MES. Otherwise, it tries to consume different licenses and has a conflict. I’ve started migrating users in this situation to Office MES.

14

I am also needing to clear users’ caches frequently. A grey screen will usually display and will be an indicator a cache clear is required.

15

Perhaps a vibe coded Chrome/Edge extension would be useful as a stop gap? We could deploy to every Epicor user and provide a big ol’ “Fix My Epicor” button that destroys Epicor’s cache and reloads it.

16

Ctrl-K then type invalid then select “invalidate cache”

image
image1103×417 45.6 KB

17

As a stop-gap, you could have users start Chrome or Edge in Incognito/In-Private mode. Upon exit, it should clear the cache.

You could also set up automatic cache clear on exit in the browser settings.

18

100% Users don’t report this crap to support because it costs a kidney and a leg just to get them to believe that your issue is real. Once support realizes the issue is due to cache, no more support happens. You just gotta clear it and hope it works! :people_hugging:

19

It happens daily, even with relatively few users. Ctrl + F5 fixes it most of the time, and the process @fvodden outlined handles the edge cases (Usually hitting the login button twice during SSO).

Agreed. Office MES for certain users is a requirement. At some point you can only conserve the DefaultUser licenses so much.

20

Adding another datapoint to this thread, we had several users that the secondary screen/slide out was blank in different screens. Clearing the browser cache resolved this for every user.