Skip to Content
CerebrumDocs
GuidesAPI referenceTrust & security

Delivery and Retry Policy

Cerebrum submits notifications through Svix. A message is successful only when your endpoint acknowledges it as described in Response requirements. Failures can be retried, so implement duplicate handling before acknowledging.

Receiver-delivery retry schedule

Svix documents the following schedule. Each delay starts after the preceding attempt fails:

AttemptTiming after the preceding failure
1Immediately
25 seconds
35 minutes
430 minutes
52 hours
65 hours
710 hours
8Another 10 hours

After these attempts, the message is marked failed for that endpoint. Removing or disabling an endpoint stops its deliveries. The Svix portal also supports manual resend, failed-message recovery, and replay of missing messages.

These are delivery-service timings, not a promise of exact arrival time, ordering, or exactly-once processing. A receiver-controlled Retry-After response header is best-effort guidance, not a precise timer. Svix also supports webhook-delivery: abort-message in a response to stop further retries for a message; do not use it as an ordinary acknowledgement.

The Cortex submission queue is a separate concern. Ordinary notifications use durable jobs with up to five attempts to submit a message to Svix, reusing a stable event identity to recover interrupted submissions. The receiver-facing schedule above applies after Svix has the message; do not add the two retry counts together as a delivery guarantee.

Durable acceptance and duplicates

  1. Verify the signature using the exact raw body and the secret for the receiving endpoint.
  2. Persist the svix-id and payload in durable storage with a uniqueness constraint on svix-id.
  3. If that ID is already stored, return a successful duplicate response without repeating the business action.
  4. Return 2xx only after the new inbox record is durable. Return a non-2xx status if storage fails so the delivery can be retried.
  5. Retrieve resources and perform slow business work asynchronously.

The same svix-id is retained when the same Svix message is resent. Do not deduplicate only on entity ID and event name: two legitimate events can concern the same entity.

See Verify webhook signatures for a runnable local durable inbox and worker, and Svix's retry reference for provider behavior.

On this page