# Fix a paused webhook endpoint

URL: https://useembers.com/help/troubleshooting/webhook-endpoint-paused/
Category: Troubleshooting
Plan: Solo and above
Updated: 2026-10-22
Last verified: 2026-10-22

> Why Embers pauses an endpoint on a 4xx, five rejected events, or exhausted retries, how to read the delivery log, fix the receiver, and resume.

An endpoint that keeps rejecting deliveries is paused rather than retried forever. Open **Integrations** in the sidebar and choose **Fix** on the **Webhooks** row, which opens the Webhooks page (`/integrations/webhooks`). The paused endpoint carries a **Paused** badge, and **Needs attention** gives its reason with **Resume**. Under **Settings**, then **API and webhooks** (`/developer/webhooks`), the same endpoint shows a banner with the reason, followed by `Correct the URL and save, or resume the endpoint, before replaying a delivery.`

> **Warning: Solo and above, administrators only**
>
> Webhook endpoints require Solo or above and a workspace admin. A workspace can have up to 10 endpoints.

## The three ways an endpoint pauses

**A terminal 4xx pauses immediately.** Any `4xx` other than `408`, `425`, and `429`, and other than the rejected-event codes below, means your receiver says the endpoint itself is wrong, and retrying would repeat the rejection. A `404` pauses after one attempt with `Endpoint paused after receiving HTTP 404.` So do `401`, `403`, and `410`.

**Five rejected events in a row pause it.** A `400`, `409`, or `422` is your receiver refusing one event's payload. That event fails after one attempt and the endpoint keeps delivering the rest. When five events in a row are refused like that with no successful delivery in between, the endpoint pauses with `Endpoint paused after 5 deliveries in a row were rejected (last: HTTP 400).`, because a receiver that refuses everything is broken. One successful delivery resets the count.

**Exhausted retries pause afterwards.** Network failures, timeouts, `408`, `425`, `429`, and any `5xx` are retried seven times after the first attempt, from 30 seconds out to about 6.3 days. When they all fail the endpoint pauses with `Delivery retries were exhausted.` The full schedule is in [webhook retries and pauses](/help/integrations/webhook-retries-and-pauses/#the-schedule).

Embers accepts any `2xx` as success and does not follow redirects, so a `301` or `302` to your real handler counts as a failure.

## Read the delivery log first

Look at the endpoint's log before changing anything: **Activity** on the Webhooks page (pick the endpoint, then filter by **Failed**), or **Recent deliveries** under Settings, then API and webhooks, filterable by state and by event type. It holds the last 30 days. Each row shows the event, its state, and the HTTP status, as in "Your endpoint answered HTTP 404"; the details view shows every attempt and the error.

| State | What it means |
| --- | --- |
| `pending` | Still being sent. It reads **Retrying** once an attempt has failed, or **Queued** until then |
| `delivered` | Your endpoint answered `2xx` |
| `failed` | A terminal 4xx (a `400`, `409`, or `422` fails the event without pausing the endpoint), or the last retry failed |
| `blocked` | Created while the endpoint was paused, disabled, or not available on your plan. It was kept, not sent |

In the app the states read in words: **Delivered**, **Retrying**, **Queued**, **Failed**, and **Blocked**.

The status usually names the fix. A `404` is a wrong path, a `401` or `403` is your own authentication rejecting Embers, a `400` is a body your handler cannot parse, and a run of `5xx` is your service failing on the request.

## Fix the endpoint

### Confirm the URL is a receiving URL

It must be public HTTPS on the default port. A URL with a `#` fragment is refused, because HTTP clients never send fragments. On a service such as Webhook.site, copy the unique receiving URL, not the dashboard URL you are viewing.

### Answer fast and answer 2xx

Embers waits about 10 seconds for a response. Acknowledge the request, then do the work asynchronously, so a slow handler does not turn into a string of timeouts.

### Verify the signature over the raw body

Verify the Standard Webhooks headers over `webhook-id.webhook-timestamp.body` using the raw request body. Parsing and re-serialising the JSON before verifying is the most common cause of self-inflicted 401s. See [verify webhook signatures](/help/integrations/verify-webhook-signatures/). In n8n, turn on **Raw Body** on the Webhook node, then [verify the signature in a Code node](/help/integrations/n8n/#verify-the-signature-in-a-code-node).

### Deduplicate on webhook-id

Delivery is at least once and retries can arrive out of order, so a replay may deliver an event your system already has.

## Resume and replay

Editing a paused endpoint's URL and saving **clears the pause automatically**, which is the path to use when the receiver moved. If the URL was right and the receiver was down, choose **Resume** instead, under **Needs attention** or in the endpoint's **...** menu.

Once the endpoint is active again, **Replay** appears on rows in a `failed` or `blocked` state. It is hidden while the endpoint is paused or disabled, so you cannot replay into a receiver that is still broken.

> **Note: Replays use current settings, automatic retries do not**
>
> An automatic retry uses the URL and signing secret captured when the event was created. A replay uses the endpoint's current URL and current signing secret, which is what makes "fix the URL, then replay the backlog" work. Earlier attempts stay in the log and the attempt count continues from the last one.

Every workspace admin receives a security email when an endpoint is created, updated, removed, paused, resumed, or has its secret rotated. It names the endpoint, the workspace, the destination hostname, who acted, and what changed, and never includes the URL path, query credentials, or the signing secret. If the email is missing, see [not receiving Embers emails](/help/troubleshooting/not-receiving-emails/).

## Troubleshooting

- **The URL will not save.** The message names the rule: `Webhook URLs must be public HTTPS URLs.`, `Webhook URLs must use the default HTTPS port.`, `Webhook hostname could not be resolved.`, `Webhook URLs must not resolve to private addresses.`, or the fragment message.
- **Saving the endpoint says "A workspace can have up to 10 webhook endpoints."** The workspace is at its limit. Remove one you no longer use.
- **Zapier, Make, or Clay stopped receiving.** They use the same signed webhook, so the same pause rules apply. If you rebuilt the Zap or scenario, copy its new hook URL, save it on the endpoint, and replay. See the [Zapier recipe](/help/integrations/zapier/).
- **Replay is missing.** The endpoint is still paused or disabled. Resume it, or save a corrected URL, first.

## Related

- [Webhook retries and pauses](/help/integrations/webhook-retries-and-pauses/): The full retry schedule and pause rules.

- [Verify webhook signatures](/help/integrations/verify-webhook-signatures/): Check the HMAC without breaking your handler.

- [Send lead events to your own endpoint](/help/integrations/webhooks/): Create an endpoint and choose its events.

## Frequently asked questions

**Does Embers follow a redirect to my real handler?**

No. Redirects are not followed, so a 301 or 302 counts as a failed delivery. Point the endpoint at the final HTTPS address.

**Do I have to replay deliveries one by one after fixing the endpoint?**

Yes. Resuming or saving a corrected URL lets new events through, but earlier failed and blocked rows are replayed with the Replay button on each row.

**How long does Embers wait for my endpoint to answer?**

About 10 seconds after connecting. A slower answer is a timeout, which is retried, and enough of them in a row pause the endpoint.
