/

Console

• English
• Deutsch
• Español
• Español – América Latina
• Français
• Indonesia
• Italiano
• Português
• Português – Brasil
• 中文 – 简体
• 中文 – 繁體
• 日本語
• 한국어

Sign in

• Application Integration

Start free

Forks and joins

Forks and joins are control points in an integration that let you specify the behaviour of a task (also known as the task's execution strategy) based on the task's incoming and outgoing conditions.

If you have enabled the canvas view, you can configure the fork and join execution policies directly in the task configuration pane.

Fork

A fork is a control point for the outgoing edges of a task. It lets you specify the execution strategy for the immediate next tasks. You can click on a fork to open the Fork configuration pane and configure any one of the following execution strategies for a task:

• Run all match: Runs all the immediate next tasks whose edge conditions evaluate to true.
• Run first match: Runs the immediate next task (in no specific order) whose edge conditions evaluate to true. For example, if there are three immediate next tasks and the edge conditions for any task (in no specific order) evaluate to true, then that task is run.

The following image shows how to configure fork for a task in the old canvas view:

If you have enabled the canvas view, you can configure the fork execution policy directly in the task configuration pane.

Join

A join is a control point for the incoming edges of a task. It lets you specify the execution strategy for the current task. When there are multiple incoming edges for a task, you can specify the conditions for which the task runs. You can click on a join to open the Join configuration pane and configure any one of the following execution strategies for a task:

• When all tasks and conditions succeed: Runs the task when all tasks and conditions are met, that is, all the upstream dependent tasks run successfully and the edge conditions of all tasks evaluate to true. If any of the upstream tasks or edge conditions fail, the task is not run.
• When all succeed: Runs the task if all its prerequisites are met, that is, all the upstream dependent tasks run successfully. If any of the upstream tasks fail, the task is not run.
• When any succeed: Runs the task if any one of its prerequisites are met, that is, at least one of the dependent tasks runs successfully. If all of the previous tasks fail, the task is not run.

The following image shows how to configure edge for a task in the old canvas view:

If you have enabled the canvas view, you can configure the edge execution strategy directly in the task configuration pane.

Quotas and limits

For information about quotas and limits, see Quotas and limits.

What's next