Delivery and rate-limit recovery
Recover cleanly from transient send failures and rate limits.
Recovery checklist
- Retry network failures with the same idempotency key.
- Back off after `429` responses instead of retrying immediately.
- Use `/api/v1/usage` to understand rate or quota pressure.
- Use the message status endpoints to confirm final delivery state.
Production recommendation
Implement exponential backoff and alert on repeated failure patterns instead of waiting for someone to report the problem.