VorloFailure Index / Rate limits & availability · warning · LangChain · OpenAI Agents SDK
Gmail API rate limit: ~25 requests/minute per user
Gmail throttles aggressively — around 25 requests per minute per user. An email-triage agent processing an inbox burst will hit this within seconds if calls are not spaced.
The error
gmail api rate limit exceeded agent
429 rateLimitExceeded gmail langchain
gmail user rate limit exceededRoot cause
Gmail's per-user quota is much lower than most APIs. Agents that loop over messages (fetch → summarize → label, per email) fire several calls per item and exceed the budget almost immediately.
The fix
Add a 2-3 second delay between consecutive Gmail calls, batch operations where the API allows it (batchModify for labels), and add exponential backoff on 429.
Preventing it next time
Design email agents to work in batches, not per-message loops, and process backlogs with a queue that respects the per-user budget.
Stop debugging this by hand. Vorlo watches your agent and, when this failure happens, hands you the diagnosis and the fix — verified by developers who hit it before you — in your dashboard, Slack, or your editor. Two lines of code:
pip install vorlo-trace · npm install vorlo-trace. Start free