> 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/stackai-project-and-beta-nodes.md).

# StackAI Project and Beta Nodes

Both project nodes reuse an existing workflow. Choose between them based on whether you need streamed answer updates, independent list processing, or conversation continuity across items.

{% 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

A child workflow with the required input/output contract and access to its run history.

## Parent and child workflows

| Term            | Definition                                                                                                                                                                 |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Parent workflow | The workflow that calls another project. It must map the child result into its own processing or visible output.                                                           |
| Child workflow  | The project executed by a project node or project-execution tool. Review its input contract, selected version, permissions, and run details.                               |
| Streaming       | Delivery of incremental events or text while work is running. Updates are not the same as a completed answer.                                                              |
| Concurrency     | Work on more than one item during overlapping periods. Completion order can differ from input order and provider rate limits still apply.                                  |
| Memory scope    | The project, node, and conversation context in which earlier exchanges can be reused. Keep unrelated users and conversations separate using the supported identity fields. |

## Choose a Project or Beta node

1. Select the workflow in the project node and map its required inputs.

![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. Enable loop mode only when the input represents multiple executions.
3. Choose the original node for its streaming behavior or Beta for independent item processing. Inspect the returned result and child run details.

You reuse the child process with the execution behavior needed by the parent workflow.

## Behavior and limitations

Beta retries eligible temporary failures. Repeated execution can repeat an external action. Map completed child outputs to the parent output explicitly; a child result is not automatically the final interface response.

| Behavior                       | StackAI Project                      | StackAI Project (Beta)                    |
| ------------------------------ | ------------------------------------ | ----------------------------------------- |
| Answer delivery                | Can return updates during execution. | Returns completed results.                |
| List processing                | Processes items one at a time.       | Supports independent parallel iterations. |
| Conversation across loop items | Shared across the list.              | Isolated for each item.                   |
| Result order                   | Follows list processing.             | Restores input order after collection.    |

## Related resources

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

[Execution Order and Node Dependencies](/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/stackai-project-and-beta-nodes.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.