Okay, have you/your customer submitted a ticket yet?
I am hoping to upgrade as soon as this is fixed which is why I am following up.
Thanks again for keeping us all in the loop and posting your findings on here Beth, truly appreciate it.
2 Likes
Ditto.
Iām watching this threadā¦
2 Likes
Yes, the customer has submitted a ticket and their Epicor PM has escalated it.
2 Likes
Okay, would you please keep us posted if possible?
2 Likes
Do they have the ādummyā token as shown how to find in this thread?
What? Are you asking whether they showed the dummy token in their ticket that they submitted?
Yes ours is gone since .15 went live. We still do have the token renewal issue, however.
What is the difference between the licensing issue and the token renewal? sorry I was unable to discern that in this thread. Both have been brought up here, right?
Correct. Our usage has most definitely gone down, I can confirm that. The getting booted after X min, I mean it is somewhat noticable but I think it is related to idle timeout in user config.
So, 2 separate issues potentially. 1 fixed, 1 lingering. 
1 Like
Are you getting āBad Tokenā in your server logs?
I have not seen this error before. Anything logged in your browser console or failed requests in your network traffic?
Iāll check, but for now:
Our license usage is back to normal. Iām more curious what exactly Bethās users are experiencing.
2 Likes
Yeah me too.
I just donāt want to split this thread into many different issues.
Browser Session Timeout - Not Inactive - Kinetic ERP - Epicor User Help Forum
It seems like the license thing is fixed, but the token issue is still happening.
3 Likes
Support confirmed with me that the fix is applied in 2023.2.28 (even though not in the release notes). We will update to the latest patch and see how it goesā¦
1 Like
the fix for the elevated license usage?
Yes. It seams like most people on this thread are on 2024.1 unlike myself. Iām not seeing the other issues that have been mentioned.
But you are seeing the elevated license?
Iām not right now because Iāve applied the hotfix. I want to be sure the next update we install isnāt going to reintroduce the issue. Itās really confusing because thereās no PRB number nor is the bug part of the release notes.
I know I just looked through them to confirm it was fixed or at least mentioned. I donāt see anything.
I wish we could get some closure on this- just whether itās in the works, fixed, etc. Itās one thing that itās happening, but Iād like to know the status of it.
Same here. Iām really just going by what support is telling me - but not sure if Iām being told the right information. Until I can see the issue fixed for myself, Iām going to assume itās still a problem.