Troubleshooting

429 Too Many Requests

LLMs Text

Fix 429 Too Many Requests

HTTP 429 means rate limiting or quota exhaustion. Clients often log:

exceeded retry limit, last status: 429 Too Many Requests

That only means retries kept seeing 429—check the dashboard to learn whether quota or request rate is the cause.

Do this first

  1. Pause the job so the client stops stacking retries.
  2. Open Usage for plan quota, 24h quota, and wallet balance.
  3. Read in-app notifications (and Telegram alerts if linked).

Message → action

Dashboard / noticeAction
Daily quota exhaustedWait for refresh or upgrade
24h quota exhaustedWait for the shown refresh time or upgrade
Plan / balance exhaustedTop up, renew, or enable wallet fallback
Too many requestsPause ~1 minute; reduce parallelism
BusyStop some jobs; wait 10–30s
Image rate limitedWait as instructed

Full detail: Handling 429 and Quotas.

Not the same as 401 / timeouts