I run on a self host container in synology
I was working on a workflow and then suddenly I started getting errors OU saying Can’t connect to n8n.
back in my workspace I can see all of my work
just this single workflow I cannot get into I delete (I exported a backup)
I restarted the container it makes no difference
tried to create a new one from import and it goes crazy
Hello @bally ,
The error msg means the database still thinks that workflow ID exists even though you deleted it.
to fix this : open your exported JSON file in a text editor (notepad) and find the "id": "..." field at the top. just delete that whole line. save it, then import again.
n8n will see it’s missing an ID and generate a brand new one, bypassing the collision.
Thanks. how do I fix the entry in the dashboard?
sometimes the title is there but when you click in it says cannot connect
sometimes it’s not there
then later it comes back
how big is that workflow?
20 nodes or so. I just cannot work out what state it thinks it’s in and can’t clean it up.
I can’t even open it to know if it thinks it’s active or not active
what i have tried now and you can test it too :
docker exec **N8N-Container-Name** n8n export:workflow --all
it won’t give you a nice list, but it’ll dump everything to your terminal screen so you can search for the ID of that workflow.
once you have the ID , you can run:
docker exec -it **N8N-Container-Name** n8n update:workflow --id=YOUR_ID --active=false
that turns it off so it stops crashing.
I couldn’t work out how to get a terminal where I can enter commands so I tried restore the docker folder from the previous date.
I used Synology Snapshot replication
the restore was fine and my list tasks were but every single task became broken like this
clicking inside the node it says
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
