> 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/overview/tutorials/insights/find-apps-using-older-mendix-versions.md).

# Find apps using older Mendix versions

Use this tutorial to find apps that still run on older Mendix versions.

### Before you start

* You need access to the apps you want to review.
* The relevant environments must already be processed.

{% stepper %}
{% step %}

### Open the components view

Go to [Dashboards → Insights](/dashboards/insights.md).

Open [Components](/dashboards/insights/components.md).
{% endstep %}

{% step %}

### Search runtime versions

Select the Mendix runtime component type.

Choose the environment type you want to review.

Filter by version when you are targeting a specific runtime range.
{% endstep %}

{% step %}

### Review the results

Identify apps that still use the older runtime.

Check the processed date if recent deployments are missing.
{% endstep %}

{% step %}

### Take action

Export the result set when you need to share it.

Or assign a task directly from the filtered list.
{% endstep %}
{% endstepper %}

### Next steps

* [Find outdated components](/overview/tutorials/insights/find-outdated-components.md)
* [Create and assign a global task](/overview/tutorials/tasks/create-and-assign-a-global-task.md)
* [Review governance readiness](/overview/tutorials/insights/review-governance-readiness.md)


---

# 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/overview/tutorials/insights/find-apps-using-older-mendix-versions.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.