> 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_0002.md).

# Mendix runtime version age

<table><thead><tr><th width="138">Check ID</th><th>COMP_0002</th></tr></thead><tbody><tr><td>Category</td><td>Maintainability</td></tr><tr><td>Summary</td><td>The version of Mendix that you use has an important effect on your app. Each version of Mendix has a different set of features, fixed bugs, and patched security vulnerabilities. Older versions of Mendix are harder to maintain because they are less compatible with new versions of widgets, modules, and Java libraries. It is recommended to keep your version of Mendix up-to-date, and no older than a year old.</td></tr><tr><td>Options</td><td>The oldest age (in days) of the Mendix version used by your app. The default value is 365 days.</td></tr><tr><td>Pass</td><td>The release date of the Mendix version used by your app is less than the value configured in this check.</td></tr><tr><td>Fail</td><td>The release date of the Mendix version used by your app is greater than the value 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_0002.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.