I’m sorry I’m very new to Epicor. What do you mean by DefaultUser licenses?
I’ll add that this behavior is not limited to browser clients - we’re still on classic 2025.2 and have deployed a forced cache clearing script that the users can run every time they get the white screen of death and it seems to help. We’re seeing this multiple times a month for a handful of users. While others are doing just fine and have no issues.
We’ve been trying to self-diagnose for repeatability and cannot find the trigger.
There is a small Reset application back to defaults option on the Kinetic log in page (personally, I wish it were labeled “Fix My Kinetic”. Epicor Ideas suggestion 
). Selecting this clears the locally cached items associated with the Kinetic environment in the URL.
Reset application back to defaults
Conceptually, this is equivalent to the smart client’s Clear Client Cache.
Epicor sells various license types to determine the type of access. Jose has a list here:
And welcome to the forum!
I will note, that there are many times that SSO login is broken that this link still leaves in a broken state and all cache/cookies must be cleared manually.
It’s a daily-regular fix me.
The Epicor Idea has moved to Gauging Interest. If you want Epicor to fix the cache issues, please vote up the idea.
Automatically Synchronize and Manage Kinetic UI | Epicor Ideas Portal
Constantly depending on the screen and user. Chrome seems to handle things better than edge for sure as far as which browser is working the best. We tried firefox as well but that one also had a lot of issues.
Yes all the time. We also use epicor identity provider and constantly have users get logged out midway through completing things due to token expiry even through they are typing at the time and it should refresh
epicor identity provider and constantly have users get logged out
We had this exact problem with Epicor IdP. Users were actively working and would randomly get “Token renewal operation failed.”
Epicor Support referenced KB0144362 – Resolving Epicor Identity Provider (IdP) “Token Is Expired” Errors in Kinetic Browser Sessions.
What ultimately fixed ours was Epicor changing the Production JavaScript IdP app auth token lifetime from 3,600 seconds to 32,400 seconds (9 hours). They had originally recommended the change, but later found it had never actually been applied and updated it from the backend.
Ive already followed the steps in that knowledge article but no joy. I might have to get another ticket in with support to have a look at your second suggestion there thanks
The second suggestion might be in KB0144482 now.
We frequently see issues that clearing the browser cache resolves. It has become my first suggestion when I see new errors/issues in the browser. This was a regular activity for our users in the smart client once kinetic was introduced. I recall a few years back hearing that the web browser would resolve cache issues (which I didn’t believe)…just changed where we have to clear the cache. I have users that put outlook reminders on their calendars to clear their cache.
I wasn’t aware of what the “Reset application back to defaults” did until now 
These kind of tips would be helpful for Epicor to share!
Every day, our office staff are experts at clearing the browser cache, using Ctrl+Shift+R, and using incognito mode. Sadly. We’ve reported this alongside dashboards, quotes, and orders over the years, as well as slow load times.
I have to do this for some users pretty regularly. They get blank screens until the application is reset.
Are you also seeing issues like duplicate lines in apps that appear and disappear, prices not populating correctly when a part is selected in Quote Entry, or date fields not flowing down to the line/release level when set at the header level? We keep seeing these odd behaviors in our environment. They don’t happen consistently and therefore can’t be reproduced at will, which is somewhat concerning because it is an excuse for the Help desk to dismiss these issues. They appear to be related to browser caching issues.
Epicor and its partners claim this issue is isolated, yet Epicor recommended “aggressive” cache clearing as a fix. When we inquired what “aggressive” meant, we were told “Aggressive here refers to regular cache clearing. You don’t have to do it on a daily basis” - well…we had to just about every day as our employees were starting to question if the data they were presented was accurate. For example, two employees in one department could run a report at the same time and get wildly different results. It’s no wonder why people were starting to doubt the system…
So, to combat this, we deployed a GP that clears browser cache every time a browser is closed. It’s not perfect and carries its own set of issues, but we’re far better off than we were before.
A mission-critical system like this should not require recurring workarounds to operate reliably, especially when the future is fully web-based.
This is a known issue and according to Epicor support it is fixed in 2026.100.9 Hotfix-R
The amount of times I have been told something is fixed in x version and it turns out not to be fixed is wild so I am not holding my breath.
Reliability and trust in the system is critical for this entire thing to work and I feel like that ideal was forgotten by Epicor a while ago.
Exactly.
CI/CD is coming in 2026.100. I truly hope they start doing something different. The quality control feels worse than any version we’ve ever seen, including 9. I wish they’d show us the stats (anonymous) of the number of tickets created for the Kinetic Version in the first 6 years vs all the other versions just to check my gut feel (I could be so far off). I understand they have more customers now, so that will skew it, but some kind of metric would be nice.
In any case, I know they see it because that’s what they said in the CI/CD webinar:
What is CI/CD?
• Kinetic releases will be delivered in smaller, monthly releases
• This replaces large, biannual upgrade cycles
• Customers will see a steadier flow of enhancements for easier adoption
Why is Epicor moving Kinetic to CI/CD?
- Faster access to new features, fixes, and security updates
- A more stable and responsive Kinetic experience
- Smaller continuous releases that help customers stay current
- Less disruptive
I wish they’d benchmark the “less disruptive” with the number of PRBs that are introduced in each realese/patch and provide something that we can measure and stay accountable too.