Webhook Troubleshooting

What “degraded” means

In the Webhooks tab, health can be healthy, degraded, or unhealthy. Degraded means webhooks are switched on but something isn’t right — typically one of:

• No subscriptions are registered with your CRM.
• A subscription exists but is inactive (often disabled on the CRM side).
• A subscription has gone quiet — no events received for 7 days.
• Events are arriving but failing or delayed at an elevated rate.

Degraded doesn’t mean data is lost. Events that arrive are queued and retried automatically; the goal here is to restore normal flow.

Triage checklist

Work down this list — most issues resolve in the first three steps:

1. Open the health panel and event log in the Webhooks tab. The health reasons and recent event errors usually name the problem directly.
2. Check the connection. Has anything changed with credentials recently — a password rotated, an admin who set up the integration leaving, permissions tightened, the app reinstalled in the CRM? Any of these breaks event verification. If in doubt, reconnect the integration — it’s safe and doesn’t delete data or settings.
3. Check subscription status with the button in the Webhooks tab, and confirm the webhook is still active in your CRM’s own settings.
4. Re-register the subscription if it’s missing, inactive, or failing signature verification.
5. Test it. Make a small edit to a record in the CRM and watch for the event.
6. Catch up. Once healthy, run a backfill if you had a long outage.

Also worth ruling out: subscription limits if some record types never registered, and field mapping issues if events arrive but fail to apply.

Still stuck?

Contact support with your CRM platform, the health reasons shown, and roughly when the problem started. Screenshots of the event log help enormously.