> 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/batch-execution-and-per-item-results.md).

# Batch Execution and Per-Item Results

Batch execution applies a project to multiple rows. Inspect each row’s status and output rather than treating a batch as one indivisible result.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F9B2kdRqUjyMIBtSa8O1Q%2FG058.mp4?alt=media&token=37b420d8-65c0-46c8-be6b-4c271af9b8e0>" %}

## Before you begin

Rows that match the project inputs, permission to run the project, and the intended stage or version settings.

## Key concepts

| Term                 | Definition                                                                                                                                                                   |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Batch row            | One input record processed through the selected project. Check the row’s status and result, not only the batch-level indicator.                                              |
| Page size            | The maximum number of records requested or processed in one page. It is not a guarantee that all records in the collection are included.                                     |
| Output mapping       | Selection of a node’s returned field for another step or the final interface. A successful intermediate result is not automatically visible to the end user.                 |
| Partial result       | Output available before all requested work completes successfully. Do not report the entire task as successful unless the operation’s contract supports that interpretation. |
| Cancellation request | A request to stop an execution. Acceptance is not confirmation that all work has stopped.                                                                                    |

## Review batch results

1. Map the row columns to the project inputs.

![Map the input and output columns before adding rows.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/t7mIQitJ9o4and6uH0Uv/assets/g058-g058-01-interface.png)

Map the input and output columns before adding rows.

2. Confirm the page of rows and execution settings before starting the batch.
3. Inspect each row’s output, citations, status, and error information.

Each completed row has a result that can be traced back to its input.

## Behavior and limitations

Confirm the selected rows and page before running a batch; starting a page does not mean every row in the dataset will run. Inspect per-row results rather than relying only on a batch indicator. Cancellation can leave work already in progress running. Check the latest row result and external destination before restarting.

## Related resources

[Batch execution](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-batch-interface.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/batch-execution-and-per-item-results.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.
