All Collections
Steps
Destination Steps
Asynchronous Flow Destination Step
Asynchronous Flow Destination Step

Used in a flow to execute another flow/process at the same time/concurrently.

Praise Magidi avatar
Written by Praise Magidi
Updated over a week ago

The Asynchronous Flow destination step is similar to the Synchronous Flow destination step, but with one main difference in that, it does not wait for the sub-flow to complete and runs concurrently. The Asynchronous Flow step calls the sub-flow and then immediately returns to process the remaining steps in your calling flow.

The sub-flow will continue running in the background. As a result, the called flow may be completed before the sub-flow is finished. Results from the sub-flow are not returned to the called flow.

Adding an Asynchronous Flow Destination Step

To add an Asynchronous Flow Destination Step, follow these instructions:

1. Click on the highlighted icon as shown in the below image.

2. The below page will appear. Select or search for a Destination step. Click on the Destination tab and select Async Flow as shown in the image below.

Configuring the Asynchronous Flow destination step

Each Asynchronous Flow step has several settings you can configure to control its operation. When you insert the step, the following dialog box is displayed to edit the relevant control values.

Flow ID

The ID/name of the flow to execute. Click on the dropdown arrow outlined in red in the above image to see a full list of all available flows and select the required one.

Alternatively, click on the icon highlighted in yellow to create a new flow. Click on the icon highlighted in green to edit the selected flow. Click on the eye icon highlighted in blue to open the selected flow.

Parameter Mappings

The fields being mapped from the record to the parameters.

  • From Path is the path to the source value within the calling flow. Have the option of using any value on the processing object.

  • To Parameter is the name of the input parameter on the flow being called.

In the example below, the first parameter references a record, the second parameter references a current parameter in the flow and the third parameter is blank which references the entire object.

Condition Path

The path to a value on the processing object that the step can check to decide whether the Flow should be executed for the current record. A true value will execute the sub-flow, and a false value will skip the sub-flow.

Source Path

The path to a value on the processing object that will be passed to the sub-flow as its data source.

Record IO checkbox

Record the actual IO value sent when the box is ticked.

Input

The input value to use. Select from the following options:

  • Record - Return the current processed record.

  • Output - Return the flow’s output file.

  • Result - Return the output of the file.

  • Original Record - Return the original record.

Did this answer your question?