Found a bug in n8n with WAIT node- important resolution needed

I’ve found a bug that is persisting in all versions of 2.4+. I upgraded from 1.x to 2.6.3 and even newer to fix it but cannot.
The bug is on self hosted, as well as n8n cloud.
Surprised this hasn’t been reported yet.

This was not present in 1.x as I built my workflows using this method and they worked fine until now. I’ve tested in a fresh 2.x workflow just the wait node with these settings to ensrue it wasn’t some upgrade issue from the workflow code. Still the error persists.

Describe the problem/error/question

Recreat with the following steps:
The WAIT node. If you set it to “on webhook call” with any settings. It works. However, if you go to Add Option and add a Webhook Suffix (anything at all), it will now no longer allow you to publish the workflow unless you delete the webhook suffix. The mere act of creating that suffix breaks whatever it is in the backend.

Interestingly, in the error itself it’s saying to fix the “other” workflow which is the same workflow in itself. Which leads me to believe there’s a constraint on the backend database with the new publish settings that’s causing a deduplication issue.

What is the error message (if any)?

Conflicting Trigger Path

A trigger 'Wait' in the workflow 'My workflow 8' uses a conflicting URL path, so this workflow cannot be activated
 
You can deactivate My workflow 8 and activate this one, or insert a new trigger node of the same type in either workflow:
https://plumehead.app.n8n.cloud/webhook/testywaters2341

Please share your workflow

Conflicting Trigger Path

A trigger 'Wait' in the workflow 'My workflow 8' uses a conflicting URL path, so this workflow cannot be activated
 
You can deactivate My workflow 8 and activate this one, or insert a new trigger node of the same type in either workflow:
https://plumehead.app.n8n.cloud/webhook/testywaters2341

Share the output returned by the last node

Last node irrelevant. It never allows you to publish. Trigger can be anything. Webhook, execute subworkflow, etc. It’s the wait node in this specific setting that is the issue.

Information on your n8n setup

  • n8n version: 2.6.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Tried it on Railway, Digital ocean, Local, N8N cloud (pro membership). All of it
  • Operating system: Mac & Windows
4 Likes

hello @alex19

Please, share the workflow.

You can select all nodes with Ctrl+A and copy them with Ctrl+C. Then, past the content after pressing the button </> with Ctrl+V.

I wasn’t able to reproduce the issue. It works fine

I encountered this error a like a week ago and fixed it by removing the Webhook Suffix,

I believe this is a bug as well,

To reproduce the issue, use any trigger and add a Wait node with a Webhook Suffix, Then publish the workflow, you will get:


  • n8n v2.7.1

Correct! This is present in every n8n I’m using- n8n cloud pro, self hosted community. Even docker images by railway and digital ocean.

ah, yes. Was able to reproduce it in 2.6.3

1 Like

Thank you for the report everyone. The fix was already merged in fix: Refine webhook conflict checks to ignore waiting webhooks by dlavrenuek · Pull Request #25395 · n8n-io/n8n · GitHub and is scheduled to be released with the next release

3 Likes

New version [email protected] got released which includes the GitHub PR 25395.

3 Likes