Skip to content
Ask a question in your own words

Why your webhook endpoint was disabled

If your endpoint keeps failing, the webhook portal disables it to stop wasting deliveries. Fix your endpoint, then re-enable it in the portal to resume.

Written by: Malaz Madani43 minutes ago1 min read

If a developer webhook endpoint keeps failing for a long stretch, the webhook portal disables it so Mando stops sending to a URL that is not working. This is a protection, not a penalty.

Why it happens

An endpoint is disabled after it fails to accept deliveries over and over: it is unreachable, times out, or keeps returning an error status instead of a success. A healthy endpoint should return a 2xx status quickly.

How to fix it

  1. Fix the endpoint so it accepts deliveries and returns a success status.
  2. Open Settings > Developer webhooks and re-enable the endpoint in the portal.
  3. Replay the deliveries it missed while it was disabled.

Frequently asked questions

Did I lose the events?

No. Re-enable the endpoint and replay the missed deliveries from the logs.

How do I avoid it?

Return a 2xx status quickly and keep your endpoint reachable. Do heavy work after acknowledging the delivery.

Does this affect Slack?

No. A failing Slack channel keeps trying and is not auto-disabled.

Related articles

Did this answer your question?

More Support

Get more support from us