When a webhook’s destination URL stops existing, LinkedScope pauses the webhook automatically so it doesn’t keep sending data to a dead address. Here’s when that happens and how to reactivate it.
- Where to see it: Settings > Webhooks
- When it pauses: after 3 consecutive permanent failures (404 or 410 errors)
When a webhook is paused
| Destination response | What LinkedScope does |
|---|---|
| 2xx (success) | Records a successful delivery and resets the failure count. |
| 404 or 410 | Counts as a permanent failure: the address no longer exists. On the third in a row, the webhook is paused. |
| 5xx, timeout or 429 | Treats it as temporary and retries later. It doesn’t count toward the pause. |
| Blocked by plan or connection | Doesn’t call the destination and doesn’t count toward the pause. |
On a daily webhook, three failures in a row mean about three days of errors. A single 404, for example during a deploy on the destination, doesn’t pause the webhook.
How to spot it
On the webhook list, a paused webhook shows the notice Webhook paused: the destination URL returned error 404 on the latest deliveries (or 410). Paused webhooks don’t get scheduled deliveries.
How to reactivate it
- Fix the destination
Publish the workflow again in n8n or Make, or generate a new URL. - Edit the webhook and change the URL
Click the pencil, paste the new URL and save. Changing only the name, frequency or conditions keeps the webhook paused. - Test it
Use the icon in the Test column to confirm the destination responds.
A clean restart
Once you change the URL, earlier errors stop counting and the webhook gets three attempts again before another pause.
Frequently asked questions
The URL is still the same. How do I reactivate it?
The webhook only comes back with a different URL. If the destination works again at the same address, remove the webhook and create a new one.
Is data from the paused period resent?
No. Scheduled webhooks continue from the next scheduled time.