Troubleshooting: BoldDesk Error 429 (Too Many Requests)
It is possible for multiple users to access a BoldDesk account. For example, a company or organization with several branches may manage all operations under one BoldDesk account. However, some may try to use a single agent account for multiple users updating the tickets or handling chats; this may lead to Error 429 (Too Many Requests) as the limit per user per hour will be exceeded. This error indicates that your browser or application has sent an excessive number of requests to the server within a short timeframe. This is a rate-limiting mechanism based on user activity implemented to prevent potential attacks. When several users access the same account simultaneously, the system can quickly surpass the permitted request threshold, leading to Error 429 (Too Many Requests).
When Error 429 Typically Occurs
- Multiple users are simultaneously logged in using the same agent account.
- A user repeatedly refreshes pages or performs rapid actions that generate many requests.
- Browser behaviour (such as cached sessions) repeatedly triggers requests.
- Browser extensions (for example, auto-refresh tools) generate background requests.
Steps to Resolve Error 429
-
Wait and Retry
The issue may be temporary. Wait a few minutes before trying again. Avoid repeatedly refreshing the page, as this could aggravate the problem. -
Clear Browser Cache and Cookies
Occasionally, outdated sessions or cookies can cause repeated requests. Clear your browser’s cache and cookies, then log back into your account. -
Inspect Browser Extensions
Certain extensions, such as auto-refreshers or aggressive ad blockers, may trigger excessive requests. Temporarily disable these extensions and check if the issue resolves. -
Switch to a Different Browser or Use Incognito Mode
This can help identify if the problem is related to a specific browser or cached session. -
Contact BoldDesk Support
BoldDesk Support can investigate whether your IP or account has been rate-limited and provide assistance in resolving the issue. If the issue persists, please contact BoldDesk Support with the following details:- Your account information
- The time when the error occurred
- The action you were performing
- A screenshot of the error (if available)
- If the users’ rate limit is exceeded in the trial accounts, the error will be displayed.
- It is not recommended for multiple users to share the same agent account. To ensure seamless and uninterrupted access, it is advisable for each agent to operate with their own individual account.
- If your application surpasses the API rate limits, the API will respond with an HTTP 429 (Too Many Requests) error. Monitor the x-rate-limit-remaining header to keep track of the remaining requests, and refer to x-rate-limit-reset to know when the limit will be refreshed. To avoid request failures, apply retry logic with exponential backoff and adjust the request rate to remain within the specified per-minute, per-hour, and endpoint-specific limits. For further details, consult API Rate Limits: Optimizing RESTful API Usage.
- Not all Error 429s are related to user limit restrictions. If you encounter this issue, please reach out to check and confirm what the issue could really be.
Troubleshooting: Common Failure Patterns
Error 429 happens immediately after login
- Cause candidates: cached sessions, multiple active sessions on the same credentials, extensions generating background requests.
- Fix: clear cookies/cache, use Incognito, disable extensions, ensure only one person is using the agent login.
Error 429 happens during high activity (ticket updates, chat handling)
- Cause candidates: multiple operators on one login, rapid UI actions, automations/tools triggering frequent calls.
- Fix: stop rapid retries, reduce concurrent activity, use individual agent accounts, contact support if persistent.
Error 429 persists longer than a few minutes
- Cause candidates: repeated retries keep extending the limit window, or the rate limit is not caused by typical UI activity.
- Fix: stop retrying, wait longer, then contact BoldDesk Support with timestamps and steps to reproduce.
Frequently Asked Questions
-
How long does Error 429 last?
Error 429 is usually temporary. In many cases, waiting a few minutes allows the rate-limit window to reset. The exact duration depends on the specific rate-limit window being applied. -
Can multiple users work in one BoldDesk account?
Yes. Multiple users can access a BoldDesk account. The issue arises when multiple people share one agent user login simultaneously. -
Is Error 429 always caused by sharing an agent account?
No. Shared credentials are a common cause, but other causes include repeated refreshes, cached sessions, browser extensions, and API overuse. -
What should be included in a BoldDesk Support ticket for Error 429?
Provide account information, exact time of occurrence (with time zone), the action being performed, and a screenshot if available. -
How can API clients avoid HTTP 429?
Monitorx-rate-limit-remainingandx-rate-limit-reset, reduce request frequency, and implement retries with exponential backoff. See: API Rate Limits: Optimizing RESTful API Usage -
Does Error 429 impact ticketing and chat equally?
Error 429 can occur anywhere the same user identity generates excessive requests, including ticket updates and chat handling, depending on activity patterns. -
Why does disabling extensions help?
Auto-refresh and similar extensions can send repeated background requests that count toward rate limits.
