> 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-outdated-components.md).

# Find outdated components

Use this tutorial to find modules, widgets, or libraries that need attention.

### Before you start

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

{% stepper %}
{% step %}

### Open component search

Go to [Components](/dashboards/insights/components.md) under [Insights](/dashboards/insights.md).
{% endstep %}

{% step %}

### Select the component type

Choose modules, widgets, Java libraries, or Javascript libraries.

Then set the app and environment filters you need.
{% endstep %}

{% step %}

### Filter for upgrade candidates

Use name, version, or latest compatible version filters.

Look for rows where the current version is behind the latest compatible version.
{% endstep %}

{% step %}

### Prioritize the work

Focus first on components that affect many apps.

Export the results or assign a task to the impacted app teams.
{% endstep %}
{% endstepper %}

### Next steps

* [Find apps using older Mendix versions](/overview/tutorials/insights/find-apps-using-older-mendix-versions.md)
* [Review governance readiness](/overview/tutorials/insights/review-governance-readiness.md)
* [Review policy compliance](/overview/tutorials/policies/review-policy-compliance.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-outdated-components.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.