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

# Mendix runtime support status

<table><thead><tr><th width="138">Check ID</th><th>COMP_0003</th></tr></thead><tbody><tr><td>Category</td><td>Maintainability</td></tr><tr><td>Summary</td><td>Mendix provides support for the last 2 versions of Mendix. For older versions of Mendix there are Long Term Supported (LTS) versions, and for newer versions of Mendix there are also Medium Term Supported (MTS) versions. For apps that are not frequently changed it is recommended to use an LTS or MTS version of Mendix. For all other apps you should always use a supported version of Mendix.</td></tr><tr><td>Options</td><td>Support Status: The support status that the Mendix version used by your app is allowed to have. The default value is 'Supported'.</td></tr><tr><td>Pass</td><td>The support status of the Mendix version used by your app is one of the allowed statuses configured in this check.</td></tr><tr><td>Fail</td><td>The support status of the Mendix version used by your app is not one of the allowed statuses configured in this check.</td></tr></tbody></table>


---

# 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.bluestorm.io/checks/component/comp_0003.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.
