Why does the Notion API return a four twenty nine error even when I stay under the documented rate limits during batch updates
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Why does the Notion API return a four twenty nine error even when I stay under the documented rate limits during batch updates
1 real search · 1 real-search pass
Notion API 429 rate_limited documented average 3 requests per second Retry-After header batch updates rate limit per integrationGoogle ↗
OBSERVEDReason
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Notion API 429 rate_limited documented average 3 requests per second Retry-After header batch updates rate limit per integration Google ↗
- API Reference · notion.notion.site
- Request limits - Notion API · share.apidog.com
- Faster retries and plan-based rate limits · creatorstoolbox.com
- Rate limit waits in the response body · creatorstoolbox.com
- Notion Updates & New Features · matthiasfrank.de
- Error Handling · nts.projects.visus.io
- @notionhq/client · npmjs.com