Hi Cameron Tomlin, good day.
Thank you for your comments. I have been in constant contact with support and have even had to escalate this with the Genesys RM, given that this has recently become a widespread issue.
The problem first emerged on January 28th and has persisted since then. Our clients have been working with multiple interactions for a long time without issues, but suddenly, the system stopped functioning correctly and began showing various errors. The only explanation we have received so far is that the
maximum token limit per request has been reached, but there is no mention of when or why these limits were changed.
Both our team and our clients are quite perplexed by this situation, as the established workflow had been working perfectly until now.
Best regards,
------------------------------
Angel Marlut
NA
------------------------------
Original Message:
Sent: 02-06-2026 07:52
From: Cameron Tomlin
Subject: Error 429 (Rate Limit) in Interaction Management - Multiple Clients Affected
Hello Angel,
I recommend working with Customer Support and following their suggestions. I have seen this issue before but it could be a number of things that are triggering the 429 error and you will need support to help dig in and find out what is triggering this error code. This will require digging into logs and the backend that we just cant do here in a public forum.
Cheers,
------------------------------
Cameron
Online Community Manager/Moderator
Original Message:
Sent: 02-05-2026 17:02
From: Angel Marlut
Subject: Error 429 (Rate Limit) in Interaction Management - Multiple Clients Affected
Since January 28th, users have been consistently encountering an Error 429 (Too Many Requests).
The logs indicate that the system is hitting the ui.token.rate.per.minute threshold within the micro.frontend namespace:
status: 429, contextId: 8fb181f6-d845-4c6a-9e4d-517da64a8598, limit: { key: "ui.token.rate.per.minute", namespace: "micro.frontend", value: 300 }
To address this, we have already performed the following troubleshooting steps without success:
Cleared browser cache and cookies.
Deleted temporary files from the %temp% folder.
Tested across multiple browsers (Chrome, Edge, and Firefox), and the issue persists in all of them.
Since these local actions have not resolved the problem and the error points to a platform-side API rate-limiting restriction, we look forward to your prompt investigation. You can find additional evidence here:
https://prnt.sc/gnNnkbsv_kPl
Have you seen this message?
Best regards
#Unsure/Other
------------------------------
Angel Marlut
NA
------------------------------