Hourly Paused-Stage Resumer

Hourly Paused-Stage Resumer

A pipeline stage that was switched off with Disable Node (or by hand on the canvas) stays off until something turns it back on. This template is that something: a cron trigger checks a release gate every hour, and the moment the gate opens it uses Enable Node to bring the stage back and run it.

What this workflow does

1. Cron wakes the workflow at the top of every hour
2. HTTP asks the gate endpoint whether the freeze is still active
3. Condition branches on the answer
4. If the freeze is lifted, Enable Node sets DeployStage back to active and saves that change
5. DeployStage runs in the same execution, because it sits downstream of the Enable Node and has not run yet
6. Disable Node then stops the hourly cron so the deploy is not repeated every hour
7. If the freeze is still on, Output reports the reason and the workflow waits for the next hour

How the flow continues

The stage is saved with active: false, so it is skipped by default and the hourly check costs nothing beyond one HTTP call. Enable Node changes the target in two places at once: it persists the active flag, so later runs and triggers see it, and it releases the stage in the current run. You do not need a second trigger or a manual re-run: the execution carries straight on from the gate check into the stage that was paused.

Use cases

• Resume a deploy, migration, or backfill stage after a change freeze ends
• Re-arm a stage that an earlier run turned off with Disable Node
• Gate expensive steps behind an external readiness signal without keeping a workflow running

Setup

Replace the two example URLs with your own gate and stage endpoints, and adjust the condition to match the JSON your gate returns. To make the stage repeatable instead of one-shot, remove the final Disable Node. To start the hourly check from another entry point, save the Cron node switched off and put an Enable Node in front of it, as described in the Enable Node docs.