The idea is:
why not to add a function to lock the activate o deactivate state?
just to avoid erroneous clicks on the “change state” button
Interesting - is this something you run into often? Don’t forget to upvote your own feature request!
1 Like
've been using n8n for two months, but this has happened twice.
The problem is that when you move it by accident, you might not notice and could disable functions that you don’t use frequently or that other people rely on.
The idea of locking or pinning the setting from the main page could help mitigate the issue.
1 Like