v1.021
about 5 hours ago
Webhook retry behavior updated to exponential backoff. The documented webhook delivery retry policy now reflects an exponential backoff schedule instead of a fixed cadence. Failed deliveries are retried up to 8 times with a delay that starts at 30 seconds and doubles after each attempt (30s, 1m, 2m, 4m, 8m, 16m, 32m, 60m, capped at 60 minutes), spanning roughly 2 hours in total — preserving today's overall retry window while reacting faster to short-lived endpoint outages. Documentation-only change; no endpoints, schemas, or payloads were modified.
🚀 New Endpoints
None
🛠 Schema & Property Updates
None
📖 Documentation & Constraints Changes
- The Webhooks section's "Accepting the webhook" guidance now describes the exponential backoff retry schedule (30s → 60m, up to 8 retries, ~2 hours total) in place of the previous "up to 25 times, with a 5-minute delay between attempts" wording.
No endpoints, fields, or types were added, changed, or removed — fully backward-compatible.