Make webhook returns 410 after 5 days idle: redeliver the Sume job

Make deactivates a custom webhook that has not been connected to an active scenario for more than 5 days (120 hours), and from then on it answers 410 Gone (Make webhooks, read 2026-10-02). A Sume job webhook pointed at that URL will not be accepted; after you reattach the webhook to an active scenario, ask Sume to redeliver the job's terminal event.

What Make says

The first three are the defaults without a Webhook Response module. The 410 case is the one that bites long-running Sume jobs only if you paused the scenario while a job was in flight.

What Sume does with a non-2xx

Sume sends one terminal event per job and retries on network errors and non-2xx responses, up to 10 attempts total with a fixed delay (30 seconds by default). Each attempt times out at 10 seconds. That is a few minutes of retries, not days. The job itself still reaches its real state whether or not the webhook lands, as the docs put it: delivery is an optimization, never the only recovery path.

Recover after reconnecting

• Reactivate the scenario so the webhook is attached to something active again.
• Read the job at GET /v1/jobs/{job_id}/status to confirm it is terminal and what the outcome was.
• Call POST /v1/jobs/{job_id}/webhook/redeliver (needs jobs:write). It re-sends the real terminal event with a fresh timestamp and signature, and works even after the automatic attempts are exhausted.
• Redeliver does not change the destination URL. If you created a new Make webhook with a new address, a redeliver still goes to the old one; a new URL means a new job.

Avoid it

If a scenario may be switched off for days, do not rely on the webhook alone. Keep the job ids in a store and poll status_url on a schedule when you switch the scenario back on. Polling is supported alongside webhooks and never resubmits paid work.