Error 404: The requested webhook is not registered

Questions
1

Describe the problem/error/question

I recently updated from 1.x to 2.x and since then I randomly get an error when calling a trigger webhook. The trigger is setup to accept POST with a path variable. The webflow is published and there is a specific procedure I can use to get it to work again, but this only lasts for one or two executions before I get the error again.

I unpublish and then immediately publish again and then I am am to trigger the workflow but on the next attempt I get the error again. Another thing I am able to do to get it working again is to drag a random node so that the status changes. I then publish again which will then work, but only for a few executions (mostly 1 execution).

What is the error message (if any)?

{"code":404,"message":"The requested webhook \"POST \" is not registered.","hint":"The workflow must be active for a production URL to run successfully. You can activate the workflow using the toggle in the top-right of the editor. Note that unlike test URL calls, production URL calls aren't shown on the canvas (only in the executions list)"}

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.11.2
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system:
1 Like
2

Many issues can appear if the migration to v2 from v1 wasn’t smooth. Try moving to a new workflow and use a new webhook node instead.

3

This is a known Cloud infrastructure issue with webhook routing after the v2 upgrade, not something you can fix on your end. Id reach out to [email protected] and mention its a tenant-level routing problem, theyll need to look at it on the backend. The toggle workaround you found is about the best you can do until they sort it out.

2 Likes
4

Hi @John_van_der_Vaart , i suppose you are facing this error while your flow is published and you are using the production URL, i recommend instead of help team reach out to support team here as soon as possible as this can be an instance level issue not your issue [email protected]

1 Like
5

@Anshul_Namdev Thanks. Yes, the flow is published and I am using the production URL. I have contacted support 2 days ago and awaiting a response.

1 Like