Feature Request Summary:
When a Zendesk webhook repeatedly receives an HTTP 410 Gone from its destination, Zendesk should automatically pause/disable that webhook (and stop retries).
Description/Use Cases:
A 410 response explicitly indicates the endpoint is permanently gone (API decommissioned or resource retired). Continuing to deliver events wastes capacity, creates noisy failures, and can trigger rate limits or incident alarms on both sides.
Common scenarios:
- We’ve migrated to a new endpoint and retired the old one.
- A third-party partner shuts down an endpoint.
- A temporary cutover leaves a legacy webhook pointing to an endpoint intentionally marked 410 to prevent use.
Desired behavior:
- If a webhook receives N consecutive 410s (e.g., 3+), Zendesk automatically pauses/disables that webhook.
Business impact of limitation or missing feature:
- Unnecessary traffic & cost: Endless retries to an endpoint that will never recover.
- Alert fatigue & noisy logs: Persistent failures degrade signal-to-noise for real issues.
- Rate-limit risk: Superfluous retries can consume platform and partner quotas.
- Operational toil: Teams must discover, triage, and manually pause/delete webhooks that Zendesk could safely auto-pause based on the 410 contract.
Other necessary information or resources:
- HTTP 410 definition: Signals the resource is permanently gone and the condition is expected to be permanent.
