Workflow unresponsive, only fixed with a GUI deactivate and activate

I have a workflow that becomes unresponsive on odd occasions.

I am guessing about once a week.

It is triggered with a Telegram bot message and works fine 75% of the time.

When it seems ‘stuck’ I have to go in to the web GUI and toggle Deactivate and Activate again.

Then, it not only works but sends through the executions that were ‘stuck’.

Any ideas how I can debug this or maybe schedule a “deactivate-then-activate” routine?

Thanks,

Paully

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.