retry_dead_webhook_deliveries

Replay every webhook delivery the team dead-lettered since an instant, once the consumer is fixed. Defaults to the last 24 hours.

Purpose

The dashboard's Replay button. After a consumer outage, every row that ran out of retries sits in the dead tab; this tool puts all of them since since back on the ladder in one call and answers with how many it retried. Omit since for the last 24 hours, the window the dashboard uses.

Every replayed row posts its event again

Confirm the consumer is healthy first — a test with test_webhook_endpoint is the cheap check — or the same rows dead-letter a second time. Only dead-lettered rows are touched; failed rows still on the ladder retry on their own.

since may not be in the future. Repeating the call after a successful replay retries nothing, because the rows are no longer dead.

Required ability

webhook-delivery:retry

Input schema

{
  "type": "object",
  "properties": {
    "since": {
      "type": "string",
      "description": "ISO 8601 instant; rows dead-lettered at or after it are replayed. Defaults to 24 hours ago."
    }
  }
}

Output shape

{
  "data": {
    "retried": 17,
    "since": "2026-09-05T09:20:00+00:00"
  }
}

since echoes the instant actually used, so a call with no argument shows the 24-hour boundary it applied.

Example prompts

"Replay everything that dead-lettered since Friday 18:00 — the CRM is back up."

"Retry all dead webhook deliveries from the last day."

"How many deliveries did the replay put back on the ladder?"

Failure modes

VALIDATION_FAILED — since is malformed or in the future.
AUTHENTICATION_REQUIRED — no authenticated user on the request.
TOKEN_MISSING_ABILITY — token lacks webhook-delivery:retry.

retry_webhook_delivery — one row at a time.
list_webhook_deliveries — see the dead tab before and after.
resume_webhook_endpoint — a paused endpoint needs resuming first.
Webhook deliveries API — the REST equivalent.