Node should be locked while executing

[g3Bg2]

Describe the bug
I can still able to edit the nodes while running.

To Reproduce
Steps to reproduce the behaviour:

1. Run some random automation tree.
2. Click on any node you can edit while automation is running.

Expected behaviour
While executing tree should be completely locked and uneditable.

Screenshots/Logs

Environment (please complete the following information):
In every environment.

[g3Bg2]

Great catch! Editing nodes mid-execution is definitely a source of confusing bugs. The solution would be to add a global isExecuting state guard that disables the node editor panel while an automation is running, and re-enables it on completion or error.

Labeled as good first issue — this is a focused UI state change, good entry point into the codebase!

[Green00101]

Hi, I’d like to work on this issue if it’s okay.

[g3Bg2]

Hi @Green00101,

Feel free to work on this issue. The issues here are bit old. Please feel free to try Loopi. If you find any issues or any updates. Please create an issue here and work on that.