Webhook 410 Gone and 3xx: what Sume does with each

Sume treats a 410 Gone like any other non-2xx: the attempt fails and is retried until the ten attempts are used. A 3xx is also a failed attempt, because redirects are not followed. Neither response disables your endpoint.

The convention comes from the Standard Webhooks spec; Sume behavior is from Job webhooks and Run webhooks, read 2026-09-30.

What does the Standard Webhooks spec say?

The spec lists 3xx as a failure, since following redirects adds load to both sides, and recommends updating the webhook URL instead. It reads 410 Gone as the server saying it no longer wants webhooks from this source, so the sender should disable the endpoint and stop sending.

How does Sume treat each response?

How do I stop deliveries I no longer want?

There is no endpoint to disable with a status code, so do not rely on 410 to stop traffic. Return 2xx and ignore the event, or take the receiver down; the attempts then run out and the job still reaches its real terminal state. The job's webhook URL is fixed at submit: the docs say Redeliver does not change the destination, and a new URL is a new job.

How do I fix a redirecting URL?

Submit the final HTTPS URL, not the one that redirects. A common case is a trailing-slash or http to https redirect. The URL is also re-validated as public HTTPS at delivery time, not just when you submit. Prove the URL with the dummy event first; see send test versus redeliver.