> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/system-maintenance-and-security/system-information/system-status.md).

# System Status

## Summary

**System status** provides information about the application's data resources across channels. It is available as a tab on the [System information](https://docs.fact-finder.com/docs/system-maintenance-and-security/system-information/system-information.md) page.

![System status tab](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-170b5b9c65f6eee7c324ca9c03964f8fd711965a%2Fimage-302.png?alt=media)

## Status details grid

The status of individual data resources is presented in a grid with the following columns:

* **Channel** — channel the data resource belongs to.
* **Resource description** — name or short description of the data resource being checked.
* **Latest modification** — date and time when the data resource file was last modified.
* **Status** — color-coded indicator and, if needed, a short status message such as `File does not exist`. Yellow means the resource is outdated. Red means the resource does not exist at the expected file system path.

Use the dropdown to view system status for one channel or for all channels. Selecting a specific channel filters the table to the relevant resources.


---

# 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.fact-finder.com/docs/system-maintenance-and-security/system-information/system-status.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.
