> 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/guides-and-quickstarts/workflow-builder/workflow-debugging-and-node-results.md).

# Workflow debugging and node results

Node results show the data and errors produced during a workflow run. Use them to find where processing first differs from the intended behavior.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FRJOvnsMntl6wmPQy7fGx%2FG032.mp4?alt=media&token=7c6389c9-d4e5-4865-b29c-93ec21ab81c3>" %}

## Inspect the node results

Run the workflow and open the input node's results.

![Input-node results for a workflow execution](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/TjBQClz5FxUU5mNoxEfG/assets/g032-g032-01-input.png)

Confirm that you are inspecting the values from the execution you want to investigate.

Expand the processing node's results and inspect its output structure.

![Processing-node output and error structure](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/wP3i5Z1Jh8ps4zl4gfGw/assets/g032-g032-02-code-result.png)

For Code, review the returned result, exit code, logs, and error details.

## Check references between nodes

Check the downstream reference against the upstream result.

![Downstream reference compared with source output](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/X79wEfZ565g4haHqqvLX/assets/g032-g032-03-mapping.png)

A wrong field path can produce a missing value even when the source node succeeds.

## Investigate a failure

When a run fails, locate the first failing node and open its error details.

![First failing node and its error details](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/kw96z4IfMxFCeqdoI9Sy/assets/g032-g032-04-failure.png)

Investigate that error before treating missing downstream output as a separate cause.

Open the failed execution in Analytics and inspect Run Details.

![Recorded execution in Analytics Run Details](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/8NP5kAwkWCzshehEHbAT/assets/g032-g032-05-analytics.png)

Use the run identifier, input, status, and node details to keep the investigation tied to one execution.

## Run the corrected workflow

Correct the problem and run the complete path again.

![Corrected workflow execution result](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/yjW93wtf5O6BXYsToFTU/assets/g032-g032-06-recovery.png)

Verify a new successful result rather than relying on a status left from an earlier run.

## Important behavior

Saved run details describe that execution. They may differ from the current draft after you edit the workflow.

## Related steps

* [Map variables and expressions](/guides-and-quickstarts/workflow-builder/map-variables-and-expressions.md)
* [Debug a recorded run](/guides-and-quickstarts/evaluations-and-observability/debug-a-recorded-run.md)
* [Error handling and fallback branches](/guides-and-quickstarts/workflow-builder/error-handling-and-fallback-branches.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/guides-and-quickstarts/workflow-builder/workflow-debugging-and-node-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.