Webhook backlog runbook
Procedure to recover webhook backlog while preserving consistency and logical ordering.
howto • updated 2026-03-15
When to activate
Activate this runbook when webhook queue size exceeds threshold and processing latency degrades.
Strategy
- Preserve idempotency before increasing throughput.
- Prioritize critical billing and payment-state events.
- Avoid blind replay without filtering windows.
Procedure
11) Measure backlog
Quantify delay by event type and organization.22) Increase capacity
Scale workers in controlled batches and monitor error rate.33) Apply controlled replay
Reprocess with clear tagging and active deduplication.44) Validate reconciliation
Confirm convergence between processed events and dashboard final state.
Expected outcome
- Backlog returns to nominal window.
- No duplicated business side effects.
- Complete audit trail for reprocessed events.