The Run workflow action allows you to modularize workflow usage by running a workflow as a task in another workflow. You can think of this type of workflow as a sub-workflow. This approach enhances flexibility and maintainability, allowing workflow to function independently, and you can integrate it as a sub-workflow based on your needs.
Here are some examples:
The list of available workflows displays only the ones you can access. It also doesn't contain any simple workflows or draft only workflows.
For the execution to be successful, the actor on the current workflow needs permission to run workflow automation:workflow:run and access to the selected workflow in the action.
The Run workflow action always runs the live version of a selected workflow. If a workflow is undeployed and available only as a draft, the task will fail with the respective error message.
Make sure you have the proper access and permission configuration for the actor to run all workflows you plan to use. For more details, refer to Manage workflow permissions.
If you don't have access to a workflow that has already been selected, this is displayed in
Workflows.
However, you can still edit and adjust the task input and any other task in the workflow.
Direct or indirect recursions of workflow executions are not allowed.
input() expression in the sub-workflow.The action result is the one defined in the sub-workflow result. For details, see Workflow results.
The Run Workflow action creates a separate workflow execution for the selected workflow. For monitoring, navigation, and cancellation behavior, see Monitor sub-workflow executions.