Content and replay
A replay is a new delivery of an existing event, with its own history.
Retention and permissions
New accepted async captures keep encrypted content for 30 days from original receipt. Reading or replaying does not extend expiry. Empty content is still available; expired or never-retained bodies cannot be recovered.
Members, admins and owners may request replay; viewers may read retained content and replay history but cannot request delivery. API keys additionally need webhooks:read for content/history and replay:write to request replay.
Confirm the current destination
Open Replay, refresh eligibility and confirm the source’s current destination. The server checks organization, permission, source revision, delivery activity, signature and expiry. No arbitrary URL, body edit or header override is accepted.
A definitive conflict requires refreshing and confirming current values again. If a response is uncertain, Retry same request preserves the original key and inputs to recover the same action. Refreshing eligibility alone does not change an uncertain action’s identity.
Understand acceptance and duplicates
A new 202 confirms queued work, not a successful HTTP send. Repeating an accepted idempotency key can return that action’s current terminal state. Check history for delivery_state, attempts, status_code, reason and ambiguity.
Replay keeps the original event ID in x-acklane-id and creates a different delivery/job. The receiver may deduplicate a deliberate replay, or process a request before its response is lost. Acklane does not promise exactly-once delivery or business processing.
Eligibility and signatures
An active delivery, paused source, missing destination, expired/unavailable body or insufficient time before expiry prevents a new replay. Invalid original signatures always remain blocked.
With validation currently on, the original event must be valid and use the same provider. With it off, incoming signature headers are not forwarded. Acklane never generates a fresh provider signature; old timestamps can be rejected by the receiver.
Attempts and history
Up to six attempts within 15 minutes, clipped to the original content expiry. The final ten seconds before expiry cannot start a new replay. Source changes can cancel queued work; they cannot undo a remote effect already started.
Replay history updates while its tab is open; use Refresh to check again. Original capture and original delivery are preserved separately from all replay jobs. Raw receiver response bodies are not displayed.