Too many requests#
Applies to v0.9Last reviewed
In short
If requests arrive faster than a speed limit allows, Zymcos refuses the request and asks you to wait. A refused request did nothing: nothing was saved, started or charged, so trying again is safe.
Every request Zymcos receives passes one check before anything happens. Among other things it counts how fast requests are arriving, so that one runaway script or stuck page cannot slow the workspace for everyone. If you go past a speed limit, Zymcos refuses the request and tells you to wait. This page says what that looks like, what it means for your work, and what to do.
What you see#
When you save or change something and the request is refused for speed, the panel shows:
Too many requests in a short time. Nothing was saved — waiting a moment and trying again will work.
Where the panel offers Try again, the button is there. Waiting a few seconds and pressing it works, because the limit is a rate and not a lock: it lets requests through again as time passes.
The message is not about your account being blocked, and it is not about how much you have made or spent. Nothing about your work is affected.
What it means for your work#
A refused request did nothing. The check runs before the request is looked at, so a refused save was not saved, a refused take was not started, and nothing was charged. That is why the message says Nothing was saved, and why trying again is safe.
Things that were already under way are not touched. A take that was being made, or an autopilot run, carries on.
For screens that only read, such as a list of files, Zymcos asks again by itself, up to twice, before showing that it could not load.
Whose limit it is#
Zymcos keeps three limits, and the refusal comes from whichever you reached first:
- Your account. What you alone send. It is set well above what a person working normally reaches.
- Your workspace. What everyone in your workspace sends together. If the whole team is working hard at once, you can be slowed by each other's traffic and not by your own. Everyone in the workspace is slowed at once when this happens.
- Your address. For requests from someone who is not signed in, counted by where they connect from. The question box on these docs pages is one example.
The question box has its own limit#
The question box on the documentation pages has a separate, smaller limit, because each answer costs us a call to an AI service. If you ask a lot of questions quickly it says Too many questions just now; wait a moment and ask again. See Asking the docs a question.
"Temporarily unavailable, please retry shortly"#
If the service that counts requests cannot be reached, Zymcos refuses requests rather than let them through uncounted. You see The server couldn't complete that. Nothing was saved, so trying again is safe. on a save, and the same rule holds: nothing was done. It affects everyone at once. See also Signing in and out for the page that says Zymcos itself is temporarily unavailable.
If it keeps happening#
If you see the message repeatedly without doing anything heavy, tell support the time and what you were doing. Say whether it was only you or several people at once: the answer tells us whether it was your account's limit or the workspace's.