# Tracing the Result of a System Failure

If you have access to trace data you will also have access to system failure reports. System failure reports are normally emailed as well, but depending on the restrictions in place in your organization they may or may not contain an enumeration of the variables set at the time of failure.

If you have access to trace data you also have access to system failure information in the server status. This is represented at the bottom of the server status page as follows:

<figure><img src="/files/fq63Wn6rVRn95bfkPJAo" alt=""><figcaption><p>Server status</p></figcaption></figure>

With all the relevant variables at the bottom of the page:

<figure><img src="/files/y79wutxsGCPwc6CV00e7" alt=""><figcaption></figcaption></figure>

This information is especially relevant to gain insights into the cause of the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> failure.

Please note that only the first failure will be recorded for performance reasons. If the <code class="expression">space.vars.X\_Agent\_Name\_Single</code> is not set to fail open, many more failures may occur. Those failures will be logged in the relevant system log instead.


---

# Agent Instructions: 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://docs.tomorrowx.com/cap/product-reference/tracing-the-result-of-a-system-failure.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.
