Execution Control – Incoming Paths
Overview
Execution Control defines how an activity behaves when multiple incoming execution paths converge.
This behavior is controlled using the Wait All Incoming setting.
Options
| Option | Description |
|---|---|
| False | The activity executes whenever any incoming path completes. Each incoming completion can trigger a separate execution. |
| All Configured Incoming | The activity executes only after all design-time (configured) incoming paths have completed. If a path is skipped at runtime due to conditional logic, the activity may wait indefinitely. |
| All Active Incoming | The activity executes only after all runtime-active incoming paths have completed. Incoming paths that are not taken due to conditions are ignored, ensuring predictable execution. |
Recommendation
Enable All Active Incoming when activities follow conditional logic (If, Switch, Decision) to avoid deadlocks.
note
Some activities (for example, AND) expose a simplified version of this behavior.