Section 07Troubleshooting & FAQ
Common issues and how to resolve them. Each entry follows symptom → cause → fix so you can match what you are seeing to the solution.
Status shows ✗ but webhooks still arrive.
- Cause: some endpoints reject the OPTIONS request (for example HTTP 405 Method Not Allowed), so the status check fails even though the endpoint does accept POST events.
- Fix: use Test instead of relying on the status check. Test POSTs a real payload, so it confirms the endpoint is receiving events.
A webhook moved to Failed.
- Cause: the endpoint failed or timed out repeatedly, so ServiceM8 deactivated the subscription automatically.
- Fix: fix the endpoint so it returns a 2xx response within 10 seconds, use Test to confirm it receives events, then select Reactivate.
"This event and callback URL is already registered."
- Cause: the same event plus callback URL is already registered as a webhook.
- Fix: edit the existing webhook instead, or use a different callback URL or event. The same callback URL with a different event is allowed.
Reactivate says the subscription is still not active.
- Cause: the endpoint is still failing or timing out, so ServiceM8 will not keep it active.
- Fix: fix the endpoint first, use Test to confirm it receives events, then try Reactivate again.
Delete is not offered for Failed or Deleted webhooks.
- Cause: Failed and Deleted webhooks are already inactive, so there is nothing to delete — the subscription is no longer live.
- Fix: use Reactivate instead if you want the webhook to start receiving events again.
Screenshot coming soon: Expanded Deleted section showing Failed and Deleted groups
troubleshootingfaqerrors
Continue reading
Need help?
Contact Get In The Cloud DevOps for help using Webhook Manager.
Still need a hand?
Our team can help you activate and use Webhook Manager in your ServiceM8 account.
