> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/operate/traces.md). # Traces Every workflow run that called a connected system. **Activity → Traces** A trace is recorded for every workflow run that calls a connected system. Where [Executions](/operate/executions.md) tells you a run failed, traces are where you look for the external call behind it. ### Controls **Search traces**, and filters for **All**, **Success**, **Error** and **Pending**. **Pending** is the state worth watching. A trace that never resolves points at an upstream system that accepted the request and never answered: the failure mode that produces timeouts rather than errors, and the one people find hardest to diagnose. ### When the page is empty Until a workflow calls a connected system there is nothing here. An empty filter gives you **No traces match**, with: > A trace is recorded for every workflow run that calls a connected system. {% hint style="info" %} This page is thin in these docs because no trace had been recorded in the workspace we documented from. The controls above are confirmed; the shape of a populated row is not. If you are working from a workspace with real traffic, trust the screen over this page. {% endhint %} ### Traces and timeouts If a workflow is timing out, look here before raising its execution timeout. A longer timeout treats the symptom. Batching the calls, or moving to the Long tier, treats the cause. See [Executions](/operate/executions.md) for the run-level view. --- # 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.fastn.ai/operate/traces.md?ask=&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.