n8n-io / n8n

Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
https://n8n.io
Other
46.31k stars 6.59k forks source link

Can't activate a workflow (URL path of node already taken) #10967

Open bastianfbr opened 3 days ago

bastianfbr commented 3 days ago

Bug Description

I was working on a startup workflow which activates all my necessary workflows when i boot n8n. The workflow stops with the error in the activate workflow node : image

However, i just checked the url path in the node and there's no second node that use the same path. I'm just blocked and can't activate all my workflows

To Reproduce

  1. Create some workflows
  2. Create a startup workflow to activate all

Expected behavior

There's shouldn't be an error as it's ok.

Operating System

Windows 11

n8n Version

1.57.0

Node.js Version

18

Database

SQLite (default)

Execution mode

main (default)

Joffcom commented 3 days ago

Hey @bastianfbr,

We have created an internal ticket to look into this which we will be tracking as "GHC-254"

Joffcom commented 3 days ago

Hey @bastianfbr

It looks like you possibly have a workflow that uses the same url for a webhook, this can happen if a webhook / trigger node is duplicated in the UI.

It looks like the error will be with item 4 so I would check what that is doing and it should shed some more light on the issue.

bastianfbr commented 3 days ago

I already checked the incriminated workflow and there's no duplicated trigger node... Very weird

Joffcom commented 3 days ago

Can you share the workflow and the data?

bastianfbr commented 3 days ago

image Had to hide all data cause of being a work workflow only

Joffcom commented 3 days ago

Hey @bastianfbr,

Sorry I should have been clearer, Can you share the workflow json and the data so we can dig into this more. Without this there is not going to be much we can do as it just looks like a case of duplicated URLs

bastianfbr commented 3 days ago

Hey @bastianfbr,

Sorry I should have been clearer, Can you share the workflow json and the data so we can dig into this more. Without this there is not going to be much we can do as it just looks like a case of duplicated URLs

I can't share the workflow so i just edit the whole flow to make you understand that there's no duplicated urls...

Blip_Blup_Blop_Bloup.json

Joffcom commented 3 days ago

@bastianfbr This sadly also doesn't help, Which node was called "Listen <>" in your workflow? I would assume the webhook node at the start but that wouldn't have any input items 🤔

If it is the webhook node do you have any other workflows in your instance using a webhook node? I have checked the error in the code and it should only be triggered if there is more than one webhook entry in the database that uses the same path. As a test what happens if you change the path from topic to something else does that start working?

bastianfbr commented 1 day ago

I have other workflows that use webhook trigger but every trigger has his own path. There's no duplicated webhook with the same path. I verified by checking one by one workflow with the UI and again by downloading all and searching for the path. There's juste one webhook pointing to the path.

If i change the path to something else it works, yes, but it still doesn't solve the issue that my path is used by a single trigger node in my whole instance and i can't activate it.

Joffcom commented 1 day ago

Hey @bastianfbr,

I would say if changing the path works it would suggest that the URL is saved somewhere or maybe cached 🤔

Has this n8n install been used for a while (pre v1 then upgraded) or is it fairly recent? We had an issue a long time ago where some nodes were duplicated in the json data which would explain this.

As another test if you delete the webhook node and add it again and set the path does that resolve the issue?

bastianfbr commented 1 day ago

This n8n install has been used for a while but after v1

Hmmm really weird, i deleted the node and added it again with the same path and... no error ? Really weird but yeah, it's ok now ?