p202 ltv webhooks revive

Make a dead webhook active again, and send what it missed in the last 7 days

New in 1.9.79
All commands

p202 CLI reference

Back to the docs

01Jobs it does

Each one is a real command line. Copy it, or open it in the builder below to change it.

revive webhook

Also: reactivate webhook, webhook stopped sending, resend missed webhook deliveries

p202 ltv webhooks revive <webhook-id>

02What you get

Pick the shape you need. People get a table. Add --json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats

03Build your command

Pick values and the command line writes itself, quoted and ready to paste.

p202 ltv webhooks revive

Set flags below; the command updates as you type.

04Flags

1 flag, plus the global flags every command takes.

FlagWhat it does
--requeuebool · default trueSend again what it did not deliver in the last 7 days (--requeue=false: new events only)

05How it works

A webhook is marked dead when one delivery fails 6 times (about an hour of retries); while it is dead its deliveries are held, never tried. Reviving keeps its id, URL and secret (the Landing Page Optimizer's pairing goes on without pairing again). Every delivery it did not deliver from the last 7 days is sent, oldest first, each with its own X-P202-Delivery: again for the failed and held ones, and the ones still pending with their failure count back at 0; a delivered one never is. --requeue=false revives it for new events only, and holds the ones still pending too. An active webhook is left as it is (revived: false). A revival waits up to 20 seconds for a cron run that is sending; a 409 means it was still sending, and nothing changed.

p202 ltv webhooks revive 3
p202 ltv webhooks deliveries 3 --status pending

06For agents

Running this from an agent

  • Read the same facts as JSON: p202 commands ltv webhooks revive --json.
  • With AI_AGENT, CLAUDECODE or another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with a hint.
  • Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure, 6 no Pro licence on the install.
p202 commands ltv webhooks revive --json
{
  "path": "p202 ltv webhooks revive",
  "use": "revive <webhook-id>",
  "short": "Make a dead webhook active again, and send what it missed in the last 7 days",
  "long": "A webhook is marked dead when one delivery fails 6 times (about an hour of retries); while it\nis dead its deliveries are held, never tried. Reviving keeps its id, URL and secret (the Landing\nPage Optimizer's pairing goes on without pairing again). Every delivery it did not deliver from\nthe last 7 days is sent, oldest first, each with its own X-P202-Delivery: again for the failed and\nheld ones, and the ones still pending with their failure count back at 0; a delivered one never\nis. --requeue=false revives it for new events only, and holds the ones still pending too.\nAn active webhook is left as it is (revived: false). A revival waits up to 20 seconds for a cron\nrun that is sending; a 409 means it was still sending, and nothing changed.\n\n  p202 ltv webhooks revive 3\n  p202 ltv webhooks deliveries 3 --status pending",
  "runnable": true,
  "tasks": [
    {
      "run": "p202 ltv webhooks revive",
      "phrases": [
        "revive webhook",
        "reactivate webhook",
        "webhook stopped sending",
        "resend missed webhook deliveries"
      ]
    }
  ],
  "flags": [
    {
      "name": "requeue",
      "type": "bool",
      "default": "true",
      "usage": "Send again what it did not deliver in the last 7 days (--requeue=false: new events only)",
      "required": false
    }
  ]
}