Daemon flow

Overview

Once started, daemon flow runs in the infinite loop until there is an exception or the flow is manually interrupted. 

For all intents and purposes, it is the equivalent of scheduling the flow to run every second but without the scheduling and without the step which initializes the resources (for example opens the connections) on each iteration. 

When to use daemon flows

The main use case for Daemon Flows is when you want to run integrations in micro-batches without scheduling the flow. The most common example is ETL from a message queue. The daemon ETL flow, where the source is a message queue, reads the fixed number of messages from the queue, sleeps for a few moments, and restarts from the last known position. 

The other common use case is when you want to actively monitor the resource, for example, a folder in the file storage, and trigger the flow when the resource is not empty, for example, there are files in the folder. 

Configure a flow to run as a daemon

Any flow can be a daemon flow but if there is a nested flow only the main nested flow can start as a daemon.

To set the flow as a Daemon simply navigate to the Parameters tab and enable the Daemon flag.