okhp3-notion-limits-and-retry

Topics in the source

• okhp3-notion-limits-and-retry
• Scope
• Rate limit contract
• Payload chunking
• Block-limit detection (Free workspace, effective 2026-09-08)
• Idempotency guidance
• Output contract
• Tooling

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Dependency-loaded reference skill. Owns how a sequence of Notion calls is paced and retried, never what to call. Always loaded through okhp3-notion-core or a sibling that needs it; never select this skill directly from a user request. | In scope | Out of scope | |---|---| | Rate-limit pacing, payload chunking, backoff and retry, block-limit detection, idempotency guidance for a bounded sequence of calls | Deciding the operation itself. Multi-thousand-item volume jobs with checkpointing and resumability are out of scope for wave 1 and belong to a future bulk-data-ops skill | Per connection: average 3 requests/second, brief bursts allowed. Via Notion MCP, stated as 180 requests/minute total across all tool calls. Search specifically: 30 requests/minute, tighter than the general limit. Never fan out parallel search calls; serialize them. Per workspace: shared across every connection on that workspace. A caller can be rate-limited while itself under its own connection limit, because another connection consumed the shared budget. On 429 (ratelimited) or 529 (serviceoverload): read Retry-After (integer seconds) and wait at least that

This is an excerpt. Refer to the complete source and its current requirements.