Notion 429 request_blocked: stop retrying, keep the Sume result

When a Notion write-back for a finished Sume job returns 429 with additional_data.rate_limit_reason set to public_api_request_blocked, stop retrying that request: Notion's request-limits page says access is restricted and retrying will not help, so contact Notion support. Keep the Sume result, park the write-back with the job id and the artifact URLs, and never resubmit the Sume job, which has already completed and been billed.

The Notion details are from its request limits page and the Sume details from Webhooks and Jobs and results, all read 2026-10-03. I did not trigger a blocked response.

Which 429 reasons can I retry?

Notion returns 429 with the error code rate_limited and puts the cause in additional_data.rate_limit_reason. Most reasons are waits: use Retry-After, add exponential backoff with jitter and cap the attempts, which the page puts at about six. The blocked reason is the exception, along with most 400s, a 401 and a 403.

What should the Sume side do meanwhile?

Acknowledge the Sume webhook with a 2xx as soon as you have durably stored the event, before the Notion call, so the 10-second attempt budget and the 10-attempt cap of job webhooks never depend on Notion's state. Dedupe on job_id. The result stays readable from result_url once result_ready is true, so a parked write-back can be replayed later from your store or by fetching the job again.

Alert a person for the blocked case rather than looping. A write-back queue that retries a blocked request forever fills with work that cannot succeed and hides the jobs that can.