Retries and Ordering

This page is pinned to sealed delivery semantics and retry policy contracts.

Canonical sources:

• Delivery semantics + retry policy: docs/rc/rc83.md
• Retry policy (pinned schedule): docs/contracts/v1/webhooks/rc83/retry_policy_contract_v1_5.md
• Delivery logs contract (attempt fields): docs/contracts/v1/webhooks/rc81/delivery_logs_contract_v1_3.md

Normative Requirements

• Your receiver should treat repeated deliveries for the same X-Zex-Event-Id as duplicates for business processing.
• Your receiver should keep acknowledgement fast after verification, and perform side effects asynchronously.

Retry policy

Retry attempt numbering and schedule are pinned by RC-83. See:

• docs/contracts/v1/rc100/fixtures/retry_policy_examples.json