---
title: "What happens when an integration fails to deliver? —…"
description: "Lemwatch retries failed webhook deliveries up to 5 times with exponential backoff, then marks the channel as degraded and emails the org owner."
canonical: "https://lemwatch.com/help/integration-retries-and-failures"
source: "https://lemwatch.com"
---

# 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

- Attempt 1 — immediate

- Attempt 2 — +30 seconds

- Attempt 3 — +2 minutes

- Attempt 4 — +5 minutes

- Attempt 5 — +15 minutes

## 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

- Integrations overview

- Test integrations

- Webhook integration


## Related

- [Help centre](https://lemwatch.com/help)
- [What integrations does Lemwatch support?](https://lemwatch.com/help/integrations-overview)
- [How do I test an integration is working?](https://lemwatch.com/help/integration-testing-and-verify)
- [Custom Webhook Integration](https://lemwatch.com/help/webhook-integration)
- [How does Lemwatch monitor XML sitemaps?](https://lemwatch.com/help/sitemap-monitoring)
- [How does Lemwatch track robots.txt changes?](https://lemwatch.com/help/robots-txt-monitoring)
- [Lemwatch pricing](https://lemwatch.com/pricing)
- [What does an alert payload look like and how is it signed?](https://lemwatch.com/help/integration-payloads-and-signatures)