If you've ever seen a message like "Too many requests" or "This application is experiencing high traffic" in your app, this article is for you. Don't worry — this is a normal, temporary safety feature, and there's an easy way to avoid it.
---
What's Happening in Plain English
Think of agentUI like a busy coffee shop. To keep the line moving fast for everyone, there's a friendly rule: no single customer can order more than a certain number of drinks per minute, and the shop as a whole has a maximum it can serve before things slow down.
When your app sends or saves data, each action is like ordering a drink. If your app tries to do a lot of actions very quickly, agentUI politely says, "Slow down — try again in a minute," so things stay fast and reliable for everyone using your app.
---
When You'll See This
You'll usually only see a "too many requests" message in one of these situations:
- You're importing or updating a lot of records at once (for example, adding hundreds of rows from a spreadsheet)
- Your app is doing something repeatedly in a loop (like checking for updates every second)
- A lot of people are using your app at the exact same moment (a viral spike, a launch, an email blast)
- Something in your app is misconfigured and accidentally repeating an action over and over
For everyday use — people clicking around, filling out forms, viewing dashboards — you'll basically never see this.
---
What to Do When You See It
Just wait one minute. That's it. The message includes a hint that says "retry after 60 seconds" — after a minute passes, everything works normally again. No data is lost, nothing is broken, and you don't need to contact support for a one-time occurrence.
If it keeps happening repeatedly, that's a sign something in your app is sending more requests than it needs to, and the tips below will help.
---
How to Avoid It
Tip 1: Save things in batches, not one at a time
This is the single most important tip. If you're importing a list of records (customers, products, orders, etc.), agentUI lets you send the whole list in one go instead of one record at a time.
- ❌ Adding 500 records one-by-one = 500 separate actions = will hit the limit
- ✅ Adding 500 records in a single batch = 1 action = no problem at all
When setting up an import or an automation, look for the "bulk" or "batch" option. It's faster, uses fewer resources, and won't trip the limit.
Tip 2: Don't make your app check things too often
If your app is set up to automatically refresh data every second or two, that adds up fast. Refreshing every 10–30 seconds is almost always plenty for a user-facing app, and it's much friendlier to the limits.
Tip 3: Be careful with automations that trigger other automations
If an automation saves a record, and saving that record triggers another automation that saves another record, you can accidentally create a loop. agentUI will stop the loop automatically — but it's better to design your automations so that doesn't happen in the first place.
Tip 4: Spread out big jobs
If you have a one-time job that's truly large — like importing your entire customer history from another system — it's usually better to do it in a few smaller chunks over several minutes than to try to do it all in one burst.
---
Quick Answers to Common Questions
Did I lose any data?
No. A "too many requests" message just means that one action didn't go through. Your existing data is safe, and you can simply try the action again after a moment.
Is my account in trouble?
Not at all. This isn't a penalty — it's a temporary speed bump that resets every minute. There's no count against your account, no warning on your record, nothing to "clear."
Will my users see this?
They might, briefly, if your app is unusually busy or if there's an issue causing it to send too many requests. Most of the time, the fix is simply to follow the tips above so the messages stop appearing.
Why does this exist at all? Other tools don't seem to have it.
They almost all do — they just don't always tell you about it. Limits like these are how cloud platforms keep apps fast and reliable for everyone. Without them, one busy app could slow down every other app on the platform.
My app is for a lot of users. Will I run into this?
Probably not, as long as your app is using batch operations where it makes sense. The limits are sized to comfortably support apps with thousands of users at once. If you're planning a launch and want to be sure, reach out to support and we'll help you double-check your setup.
---
When to Contact Support
You should reach out to support if:
- You keep seeing the message during normal everyday use (not bulk imports or automations)
- You've followed the tips above and you're still hitting the limit
- You're planning a one-time large import or migration and want guidance on the best way to do it
- You're about to launch or promote your app and want to make sure it's set up to handle the traffic
When you contact us, please include:
- The name of your workflow
- Roughly when you saw the message
- What you (or your users) were trying to do at the time
We can look at the activity behind the scenes and tell you exactly what's happening.
---
The Short Version
- "Too many requests" is temporary and harmless — wait one minute and try again
- The biggest cause is doing many small actions instead of one batch action
- Use batch options when adding or updating lots of records
- It's not a penalty — it's a safety feature to keep your app fast
If you have questions, our support team is happy to help.