I've noticed that when a scheduled event runs concurrently with a new package transport or node restart, it stays in a "running" state for approximately 2 hours, preventing new events from being triggered. Has anyone else encountered this issue? If so, could you share any known solutions or temporary workarounds that might resolve this problem?
asked
Peter Mudde
1 answers
1
The scheduled events are running in the task queue, maybe you can manipulate the data in the queue with an after startup microflow?