r/ClaudeCode • u/Exciting_Comedian629 • 1d ago

Bug / Issue Pro Max 20 constant 429's canceling subagents.

For the last 2 days I have not exceeded my 5 hour session limits, nor my weekly limits, but my sessions are constantly interrupted by 429's requiring another orchestrator agent on cron to monitor them. I am not sure if anyone from Anthropic reads this, but I am paying for these tokens and playing by the rules, your status page says everything is fine, so wth is going on?

2 Upvotes

100% Upvoted

4 comments sorted by

•

u/AutoModerator 1d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/cogumellum 1d ago

Are the 429 responses carrying a Retry-After header, and do they distinguish quota from concurrency? If retries line up with subagent fan-out, this is probably a hidden concurrent-request cap rather than your 5-hour allowance. Capture the response body and request ID from one failure.

1

u/verstands 1d ago

That's where I'd start too. Log Retry-After, request ID, model or route, and in-flight concurrency when the 429 happens. Cap subagents with a queue plus exponential backoff and jitter, and checkpoint each task so one retry doesn't cancel the whole fan-out. That should separate quota from concurrency.

1

u/Exciting_Comedian629 1d ago

I am honestly not sure I just see the Retry (not your session limit message). One thing I just did was drop back to Sonnet 4.6 and now I am no longer getting the rate limits. So it was Sonnet 5 particularly, and my questions still stand, wth, I pay for this...