> For the complete documentation index, see [llms.txt](https://flow-core.gitbook.io/flow-core-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flow-core.gitbook.io/flow-core-docs/documentation/troubleshooting.md).

# Troubleshooting

Use this section when something does not run, does not show the expected data, stops early, or costs more than expected.

Troubleshooting pages start from symptoms and move toward likely causes, first checks, fixes, and deeper references.

## Start With

| If you see...                                         | Read                                                                                                |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| A common beginner or authoring failure                | [Pitfalls](/flow-core-docs/documentation/troubleshooting/pitfalls.md)                               |
| A graph that does not fire, stops, or uses wrong data | [Graph Debugging](/flow-core-docs/documentation/troubleshooting/graph-debugging.md)                 |
| A Behavior Tree that chooses the wrong branch         | [BT Debugging](/flow-core-docs/documentation/troubleshooting/bt-debugging.md)                       |
| Runtime spikes, polling cost, or queue buildup        | [Runtime Cost Monitoring](/flow-core-docs/documentation/troubleshooting/runtime-cost-monitoring.md) |

## Pages

* [Pitfalls](/flow-core-docs/documentation/troubleshooting/pitfalls.md): Quick symptom-first checks for graph startup, Blackboard data, chains, previews, lifecycle, saving, and performance.
* [Graph Debugging](/flow-core-docs/documentation/troubleshooting/graph-debugging.md): Diagnose runtime graph behavior from symptoms, causes, checks, and fixes.
* [BT Debugging](/flow-core-docs/documentation/troubleshooting/bt-debugging.md): Diagnose Behavior Tree priority, condition, decorator, service, and result routing issues.
* [Runtime Cost Monitoring](/flow-core-docs/documentation/troubleshooting/runtime-cost-monitoring.md): Use profiling and runtime observations to interpret execution cost.
* [Performance and Failure Modes](/flow-core-docs/documentation/troubleshooting/performance-and-failure-modes.md): Connect common runtime failure modes to practical prevention and fixes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flow-core.gitbook.io/flow-core-docs/documentation/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.