404 My production webhooks are returning 404 'not registered' on my Cloud instance at andresde.app.n8n.cloud even though my workflow is Published. Please re-sync the webhook registrations for my workspace

Questions
1

Describe the problem/error/question

<!-My production webhooks are returning 404 ‘not registered’ on my Cloud instance at andresde.app.n8n.cloud even though my workflow is Published. Please re-sync the webhook registrations for my workspace.- n8n Cloud users: If you’re experiencing issues with your cloud instance (e.g., can’t sign in, instance unavailable), please contact support at help@n8n.io →

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @agdm00 Welcome! Have you tried unpublishing your flow? and then publishing it back? or removing the webhook node and adding a new one? Although if this does not work you should be contacting the support team.

4

Hey @agdm00, this is definitely one of the most frustrating issues on n8n Cloud. As Benjamin and Anshul mentioned, it’s a webhook registration desync (the database says the flow is active, but the active memory/router doesn’t have the route registered).

If the standard unpublish/republish doesn’t force a cache clear, try this workaround:

  1. Select all nodes in your workflow.

  2. Copy and paste them into a brand new workflow.

  3. Save and activate the new workflow (this forces the system to generate a completely new Webhook ID and re-register the route from scratch).

  4. Update your external app to point to this new Webhook URL.

Side note from an infrastructure perspective: This specific 404 error is exactly why setting up external monitoring for webhook failures is so critical. Because the webhook never triggers, n8n records 0 failed executions in the logs, leaving you completely blind while your external apps get 404s.

Hope the duplicate trick gets you back up and running quickly! Let us know if it works.