My customer is in the cloud and we are seeing this issue get worse. You can be in a session actively working on something and it times out on you…boots you right out! It’s frustrating!
4 Likes
Do you have a problem number or hotfix for 2024.1? We have the same issue on-prem
The hotfix @mbayley posed is only for 2023.2 
1 Like
our cam replied that no customers are experiencing this issue, even though screenshots of this thread were provided… 
5 Likes
I wasn’t given a problem number for their hotfix.
Their hotfix removes the getServerCurrentTime method and IsTokenValid request from the javascript. I think you are fairly safe to short circuit that method as I’ve done above (assuming this is the same issue in 2024.1).
I still haven’t seen the bugfix in the release notes.
1 Like
I honestly dont see why this would only impact on-prem like support is suggesting. I dont even see the hotfix available to download for on-prem customers on Epicweb, like other hotfixes.
Open Devtools and within sources search for “DUMMY_TOKEN” in main.86964f04c6bb2034.js. If you get 1 result, you likely will have the same issue (using Azure AD or Epicor Idp).
1 Like
Yes, that’s how ours looked like in 2023.2.26. Escalate your case if you haven’t already. Tell them to look at CS0004563483
4 Likes
Awesome, thank you! Great work identifying this issue!!! We are still fighting on the price of the additional licenses we had to purchase.
3 Likes
That sucks. I hope they make it right for you.
I’ll keep this post updated when I see a bugfix come through.
1 Like
No, we don’t have a hotfix.
1 Like
Beth can you have your customer check the above? The main script in dev tools? The number may be different but it should just start with main.
1 Like
Now that this thread has been going on a while, I remembered we had to buy a few more around this time as well. We were getting close anyway, but I bet this was part of the reason we needed it as well.
We actually need them now though, so for us it’s a wash I guess.
2 Likes
Hey everyone,
Just wanted to provide some info I got from support yesterday regarding a timeline on this issue being fixed for customers that are on the cloud and using Kinetic.
There’s a planned fix for this in 2024.1.15 that’s being deployed in the next two weeks. Here’s a screenshot of the entry on the changelog for the upcoming release:
The hotfix was mentioned by support when we were discussing the issue, but I guess it doesn’t work with our environment since we are using IdP logins.
I don’t know if this addresses all of the issues at hand regarding what everyone has been experiencing, but it seems like it will correct the random timeouts/multiple licenses being consumed by a single user that’s been ongoing for quite awhile now.
I’m not sure what the long term resolution is going to be for anyone who is on a 2023 instance/on-prem/Classic. Hopefully this applies across the board for everyone. (Wishful thinking 
)
If I get any additional info from them I’ll be sure to give a heads up here as soon as I hear back again!
6 Likes
1 Like
So does this patch fix it for IdP users whereas the hotfix didn’t?
Am I understanding that correctly?
That’s the way I understand it. I ran the hotfix that support provided a couple weeks back, and it got things working for a couple days but by the end of the week it was back to happening again unfortunately.
I inquired if they had updated the hotfix at all as to make it a more permanent solution but never really got a firm answer on it and was pointed to the upcoming update for next steps.
That’s weird. Did you update to another version after applying the hotfix? I believe the hotfix would have to be reapplied if so.
We have decided to hold all updates until we see the permanent fix in the change log.
1 Like