Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kash.bot/llms.txt

Use this file to discover all available pages before exploring further.

HTTP status: 429 · Title: “Replay limit reached”

​
When it fires

POST /v1/webhooks/events/{id}/redeliver was called for an event that has already been replayed up to its cap (default 5).

​
Why it happens

  • A bug in the consumer kept calling the redeliver endpoint in a loop instead of fixing the underlying delivery problem.
  • An automation re-replayed without checking past attempts.
  • A genuinely persistent need to replay an event many times — uncommon and usually signals an upstream issue.
The cap exists to stop a compromised key from looping the replay endpoint to flood its own customer endpoint or our delivery worker.

​
How to fix

  • Stop calling the redeliver endpoint for this event id. The cap is per-event, so other events still replay normally.
  • Fix the underlying delivery failure first — check the event’s delivery status via GET /v1/trades/:id (the webhookDelivery field) or via kash-admin webhooks trace --event-id <id> (operator command).
  • If you legitimately need more replays for one event (e.g., recovering from a long endpoint outage), contact support — we can clear the counter manually.