i’m referring to the issue here:
Describe the issue/error/question
Hey guys, I’m new to n8n, but I’ve tried the windows app and set-up a workflow successfully.
I’ve installed n8n via Docker on linux, so that I can have the daemon running all the time. Managing it via the web interface.
I’ve followed the instructions, and got n8n set-up, but I’m getting various errors when trying to import and save workflows.
When I import workflows, they import correctly, but I’m unable to edit any of the nodes. It’s almost like the nodes a…
As the topic is closed already, i’m opening a new one.
Being on 0.203.1 now the issue stated in the link above is not fixed for me at least on a following workflow:
open a workflow
execute workflow with pinned data on the first node
try to edit some node settings
save is not working (workflow was changed by another user)
I’m the only user in my installation. Please help, as the issue prevent me from developing further on the project I have.
Edit: my setup
n8n version: 0.203.1
Database you’re using (default: SQLite): MySQL
Running n8n with the execution process [own(default), main]: main
Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
Turns out I’m seeing the same error. I’m using npm to run n8n 0.203.1 with the default execution process, with Postgres. I’m most certainly the only user in my deployment. Going back to the
Workflows dashboard and clicking on the workflow where I saw this error takes me right back to a blank slate, so workflows are definitely not being saved.
Hi all, I am very sorry for the trouble.
I know our engineering team was discussing this problem the other day. Perhaps
@netroy can share an update on this and confirm if any further details are needed here?
I met this bug too. And I simply tested
0.203.0, both these two version have this bug.
0.202.1 is working properly, I have downgraded to
Oh that’s quite alright! No damage done. I think I’ll try downgrading my
n8n installation down to
0.202.1 - is that going to cause any issues with schema migrations?
@rudimk. Also, from following the internal conversation I can confirm we’ll (temporarily) remove the feature causing these problems with the upcoming release: fix: Disable workflow locking due to issues by krynble · Pull Request #4708 · n8n-io/n8n · GitHub
Got released with