Managing flows

These basic actions may be done via the UI, and via the API. Note that when you start a Flow, the latest Flow version is used.

To copy a Flow within the same Workspace, navigate to see your Flows. Then click on the corresponding icon to open the settings menu of the selected Flow:

Alternatively, you can navigate to the Flow itself by clicking on its name, then switch to Implement tab (1) and click the command (2) to copy it to clipboard, and create a copy of the Flow via the API:

Top level admins may see the option to change the flow type to Real Time. There is a cost associated with real time flows, and in most cases they are not required. If you think you need a real time flow, use the in app Chat to reach out to the Customer Success team for assistance.

You configure the platform to send you emails for errors in your flows. Note that for errors that repeat you will not receive an email for every error. Depending on the error type you will receive one email per hour, or one per 24 hours.

To subscribe to errors, use the settings menu (1) of the corresponding Flow and click Subscribe to Errors (2):

Use the same page to unsubscribe.

You can schedule your flow to run using CRON expressions. This can only be done in Draft mode.

Note: You cannot schedule a flow if starts with a Webhook component. If you need to schedule a webhook flow, add a Simple Trigger component at the start.

While editing the Flow, switch to Settings tab (1), use CRON expression to schedule the Flow, and click Save:

The default CRON expression is */3 * * * *, meaning "every 3 minutes". The positions in the expression from left to right represent:

The month and weekday abbreviations are not case-sensitive. Also, the following special characters are in use:

EXAMPLE: * * * * * means every minute of every day of every week, etc.

EXAMPLE: * * * * MON,WED,FRI means every Monday, Wednesday and Friday.

EXAMPLE: * 2-5 * * * means every hour between 2 and 5 AM.

EXAMPLE: * * * */2 * means every two months.

Feel free to use the hint below the CRON expression field for reference. Otherwise, you can always click Run Now or use a:

request to run the Flow on demand.

The Next Occurrences pane will help you judge whether your CRON expression was written correctly:

The Platform allows you to create different versions of a Flow and switch between them if required. There are two Flow states in the Flow editing process: draft mode and published version. Every time you publish a draft, you create a new Flow version.

In the draft state you can edit or add steps, verify credentials, retrieve data samples and configure CRON expressions. You can then publish the draft and test-run your flow. A new draft is created when you create a new Flow, or edit an existing one. This means that you can safely edit a draft version without impacting an active flow.

To publish a draft, use the Publish button as per below. This button will only be active if all of the required steps are completed.

Use the History tab (2) to see a list of all versions of the flow including the published (1) version and all historic versions.

You can revert to an old version by selecting it, creating a draft and publishing it.

You can work on one draft of a given Flow at a time. If you try to create another one, the Platform will ask you if you want to overwrite the existing one.

When you publish a draft of an active Flow, it stops immediately, and restarts as a new version.

A Snapshot is the data saved by a Component during its execution. When the Component is run next time, it will read the Snapshot to continue the process from the point it finished last time. You can manually reset this Snapshot, so the Component starts from scratch next time. Note that you can only reset Snapshot for a stopped Flow. To do this, click the settings button on the Flow (1), and select Reset Snapshot (2):

This is the only way to delete an existing snapshot.