Workflow isn't working!

Questions
,
1

Describe the problem/error/question

Workflow: “Sponsorship Onboarding Automation” (ID HFDK6rOZThbDst4B), instance freewayphx.app.n8n.cloud, project “Personal.” Production webhook consistently returns 404 “not registered” even though the workflow is confirmed active (verified via API and the UI toggle, cycled multiple times). Recreated the webhook trigger node entirely with a fresh webhook ID and path — same error persists. Manually executing the workflow via n8n’s own execution API works correctly end-to-end, confirming the workflow itself is valid; only the production webhook route fails to register.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: 2.31.5
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system:
2

Hi @Daniela_Santangelo
On 2.x the active state is the publish state, and the production webhook is served by the published version of the workflow, not by your current draft. Recreating the trigger node with a fresh webhook ID and path only changed the draft, so the published version is still registering the old path and the new URL comes back as not registered. It also explains why the execution API works, that runs the draft.

Open the workflow and look at the Publish button in the canvas header. If it shows unpublished changes, publish it (Shift + P) and confirm in the modal, then call the production URL again. The history icon next to it shows which version is actually live, worth checking that it contains the new webhook path.

If it is already published with nothing pending and the production URL still 404s, that part is Cloud-side routing, email help@n8n.io with your instance name and the workflow ID and ask them to re-sync the webhook registrations for your workspace.

3

I think this is a recurring pattern, there are several other recent threads with the identical symptom (Published workflow, 404 not registered on the production webhook, execution API works fine). If republishing doesn’t fix it, go straight to help@n8n.io and mention it.