My workflow works perfectly when called via the Test Webhook URL.
However, the Production Webhook URL returns 404 Not Found.
The workflow shows as “Published”, but the status toggle never becomes “Active” (stays inactive).
I have already tried:
Changing the webhook path to a completely new value (same issue)
Unpublishing and republishing
Creating a new workflow from scratch (same issue)
Re-authenticating all credentials
Refreshing and waiting for propagation
The issue is not related to the workflow logic (test mode proves it works).
It appears to be a backend registration problem where production webhooks are not properly registered on the n8n Cloud routing layer.
Request:
How can I force a full re-registration of production webhooks for my workspace?
Is there a way to manually sync or reset the webhook router on n8n Cloud?
No workflow details or JSON are needed for this – just the infrastructure behavior.
Hi @amnih Welcome!
You have tried all the things you could have done to fix the issue yourself on client side, now i feel the issue is related to your n8n instance, please consider contacting n8n support here:
Also giving your cloud instance a restart is something you can try with downgrading or upgrading to beta if available.
welcome to the n8n community @amnih
I understand you’ve already tested several scenarios, but we can’t move straight to the infrastructure angle without first confirming whether the workflow starts with a Webhook node and whether it actually shows the Production URL, or whether the same error appears with only a single Webhook node, for example. It would also be useful to see the response headers / request URL actually being hit.
Those details would help separate URL/publish state mismatch from a real infrastructure problem.
@amnih published ≠ active — you gotta flip the toggle to Active after publishing, the production webhook only registers once the workflow is actually active. if the toggle won’t flip, try importing a minimal webhook workflow to see if activation works at all:
import that, hit activate, and test the production URL — if that one also won’t activate then it’s def an instance-level thing and you should email help@n8n.io with your workspace ID.
