> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/workflow-execution/nested-workflow-version-and-environment-selection.md).

# Nested Workflow Version and Environment Selection

A child workflow can use a different version or environment from its parent. Explicit selection makes nested behavior easier to reproduce.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FetyoI7AyLxJddyY1BdoL%2FG025A.mp4?alt=media&token=5437a55e-716b-4387-9937-79b098e9f9d7>" %}

## Before you begin

The child project’s saved versions and the environment required by the intended execution path.

## Key concepts

| Term              | Definition                                                                                                                                                 |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Draft             | The editable project configuration before or apart from a selected published release. Saving a draft does not necessarily change what published users run. |
| Published release | The selected project version made available through a published execution path. Confirm the active release after a publication or promotion action.        |
| Child workflow    | The project executed by a project node or project-execution tool. Review its input contract, selected version, permissions, and run details.               |

## Configuration options

| Option          | Purpose                                                                   | Behavior                                                                          |
| --------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| Project version | A specific saved configuration of a project.                              | Select it explicitly when a result must be reproducible.                          |
| Environment     | A named configuration context for variables, secrets, and deployment use. | Different environments can reach different services or use different credentials. |

## Select the child workflow version

1. Inspect the calling node’s project and version settings.

![Select the child workflow in the Beta node and review its input and loop settings.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/sTvd1OsSusbVba1u5Vv9/assets/g025a-05-beta-setup.png)

Select the child workflow in the Beta node and review its input and loop settings.

2. Check which environment belongs to the selected child version or stage.
3. Run the parent and inspect the child run’s configuration and resolved outputs.

The child executes with the version and environment intended by the caller.

## Behavior and limitations

Do not assume the parent’s environment overrides every child setting. Review the selected child version and environment in the calling node and confirm them through the resulting run. Use a concrete saved version where the caller supports it when repeatable behavior is required.

## Related resources

[Compare the StackAI Project and Beta nodes](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/compare-the-stackai-project-and-beta-nodes.md)

[Execution Order and Node Dependencies](https://docs.stackai.com/technical-reference/workflow-execution/execution-order-and-node-dependencies.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/workflow-execution/nested-workflow-version-and-environment-selection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
