Hi, I am experiencing an issue with the cron trigger and somehow related with the scheduler.
I noticed that when I save the workflow the cron trigger not always run with the newly saved settings.
By settings I mean the configurations of the blocks.
I found my workflow running with data in the blocks that were there before saving. I manage to get around the problem by restarting the container, which in turn I believe starts the scheduler with the new settings.
I wanted to provide more clear information like logs and execution history but I’m not sure where to find those.
Please let me know what more information I can provide to help with this and I will gladly provide it.
Hm, very strange. I will go through the code which activates/deactivates a workflow to see if I can find something that could cause this issue.
Anything else you can tell me about these workflows which cause issues that could be important? Like, do they only have one Trigger-Node or multiple ones? All of the same type or different ones?
One time I also noticed that executions ran in strange times with old configurations in other blocks. I double checked the time zone and the cron settings in all trigger blocks. I assumed they were queued up with old settings and delayed to run in a point in time where I had already changed the settings.
Yes you are totally right. There is a huge bug with multiple Trigger-Nodes. It always activates all of them but just deactivates one. Will try to fix asap and release a new version.
Hi @jan I ran a couple of tests based on your description of the problem, with multiple triggers, and it seems to be working. Thanks a lot for the fast response!
