Sub-workflow

Use Sub-workflow when one workflow should hand work to another saved workflow and wait for its result before continuing.

Note: Sub-workflow is not yet available in the workflow editor. Existing workflows that already use this step continue to run; new steps cannot be added from the dashboard until configuration UI ships.

​

When to use it

Use a Sub-workflow step to reuse a workflow you already trust, split a large process into smaller workflows, or call the same workflow from multiple parent workflows. The parent workflow pauses at the Sub-workflow step while the selected workflow runs. When the child workflow completes, the Sub-workflow step stores the child result so later parent steps can reference it.

​

Configure the step

Add Sub-workflow from the advanced step group. Choose the workflow to run. Map parent values into the selected workflow’s start inputs. You can use fixed values or variables from earlier parent steps. Use When the step fails to choose whether a failed child workflow should stop the parent workflow or let the parent continue.

​

Runtime behavior

The child workflow appears as its own workflow run in logs and remains linked to the parent run. If the parent run is cancelled while the child workflow is active, Fetch Hive also cancels the child run. If the child workflow fails, the Sub-workflow step is marked failed. Terminate Workflow stops the parent run. Continue records the failure on that step and lets later parent steps run.

​

Tips

Keep the child workflow’s start inputs clear and stable. A Sub-workflow step is easiest to maintain when the parent only maps the values the child workflow actually needs. Open workflow logs when debugging. The parent run shows where the Sub-workflow step happened, and the linked child run shows the detailed steps inside the child workflow. See also: Error Handling, Logs, and Creating and Editing