Skip to main content

Launch Week Day 5 - Restartable Flows

ยท 3 min read
Guillaume Bouvignies

Restartable Flows

Last day of our launch week today (we know it's sad). Before saying goodbye, we want to tell you about features that will help you in your ETLs, with restartable flows (this article) and S3 integration for data pipelines.

The principle is simple: once the flow is executed (whether in test or deployed), you have the possibility to restart it from any node (step, iteration of a for loop, or branch).

For testing, it's great because you can restart from a specific node without recomputing the flow.

For prod, it's great because you can skip the already completed part of the flow avoiding duplicate actions (in particular, ensure data integrity).

This feature is part of the logic of the different ways to iterate over a flow (testing the entire flow, only one step, or up to a certain step).

How to restart a flow from a given nodeโ€‹


In the flow preview page, just select a top level node and a "Re-start from X" button will appear at the top, next to "Test flow".

How does it work?โ€‹

To understand how Windmill can easily restart a flow from any step, it's important to have in mind how a flow is modeled in the backend. All the details are well explained in this other blog post, but what's important for the sake of this post is that each flow step is a normal Windmill job being executed by the flow state machine. Only the ID of this job will be tracked in the flow status that triggered it (a flow step can be seen as a pointer to any job).

When a flow is restarted from a step (let's call it Step A), the logic running in the backend is simple. A brand new run for this flow will be created (as if you were starting it from the beginning), but prior to executing it, Windmill will "copy" the status of all the predecessors Step A form the original flow into the new flow status. When starting the execution of this flow, the first step pointing to the original flow steps will already be in a "Success" state, and the state machine will jump straight to Step A as the first step being in a "WaitingForPriorSteps" state. Step A will be added to the execution queue and from there the flow continue like any other flow.

In the end, the steps prior to Steps A are "shared" between the 2 flows (the initial one and the restarted one), and all the steps after Step A (included) are specific to each run.

Learn moreโ€‹

To learn more about the launch week, you can visit our dedicated page or subscribe via our newsletter sign up form.

For more details on instant preview & testing, see:

Windmill Logo
Windmill is an open-source and self-hostable serverless runtime and platform combining the power of code with the velocity of low-code. We turn your scripts into internal apps and composable steps of flows that automate repetitive workflows.

You can self-host Windmill using a docker compose up, or go with the cloud app.