What happens when an integration fails to deliver?
Lemwatch retries failed webhook deliveries up to 5 times with exponential backoff, then marks the channel as degraded and emails the org owner.
Quick answer#
On a non-2xx response Lemwatch retries the delivery 5 times with exponential backoff (30s → 15min). If all retries fail the channel is marked degraded, and the org owner receives an email with the failing endpoint and the last error.
Retry schedule#
Where to find it in Lemwatch#
Settings → Integrations → Delivery Log — every attempt, status code, and response body.
FAQ#
Do you retry 4xx errors?#
No — 4xx means your endpoint rejected the payload; fix the config and re-test.
Can I replay a failed delivery?#
Yes — click Replay on any log row.
Related#
Related Articles
What integrations does Lemwatch support?
Lemwatch routes alerts to Slack, Discord, Teams, PagerDuty, Telegram, Google Chat, Mattermost, Rocket.Chat, ntfy, generic webhooks, and email.
How do I test an integration is working?
Every integration has a Send Test button that fires a synthetic incident payload to the channel and confirms delivery in the UI.
Custom Webhook Integration
Send alert data to any HTTP endpoint via custom webhooks. Slack and Discord URLs are auto-routed when used in escalation steps.
What does an alert payload look like and how is it signed?
Webhook payloads are JSON with incident, site, severity, and evidence fields. Every request is signed with HMAC-SHA256 using your channel secret.