I have a workflow that takes several hours to run, but the exact duration varies every time. Currently, I’m using a Schedule Trigger, but it’s inefficient—if I set the interval too long, the workflow sits idle; if I set it too short, I risk overlapping executions.
Is there a standard way to make a workflow “self-restart” or loop back to the beginning only once the final node has successfully completed?
I’m looking for a way to ensure 100% uptime without manual intervention or guestimating schedules. Thanks!
Use a webhook as last node, and then add a webhook trigger to the start using the same webhook url’s. So at the end, the it will trigger a new flow via webhook.
You can also send specific information with the webhook, allowing you to use that in the next trigger too, which you can use as context for conditions (to skip certain things for example, or take a different route).
Additionally to the above, incase the workflow error’s out, you can still reboot it based on some logic of the type of error whether transient (temporary like network related etc) or not using the below example with the Error Trigger.
Make sure to point this workflow again to itself for error handling. Go to the workflow settings and set the Error Workflow property:
