> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/scan-and-analyze-with-ox/analyzing-scan-results/applications/managing-applications/irrelevant-applications.md).
# Irrelevant Applications
You can review applications that are excluded from the active application inventory, understand why they were marked as irrelevant, and identify repositories that may need to be restored or cleaned up.
Applications can become irrelevant automatically based on repository status or activity, or they can be marked as irrelevant manually by an administrator.
The following reasons can cause an application to become irrelevant automatically:
| Reason | Description |
| -------------------------------------------------- | ----------------------------------------------------------------- |
| No code changes in the last *n* days | The repository has not changed for the configured number of days. |
| Archived Repo | The repository is archived in the source control system. |
| Repository has been set by client to be irrelevant | An administrator manually marked the application as irrelevant. |
| Repository is empty | The repository does not contain source code. |
| Branch does not exist | The configured branch no longer exists. |
| No Relevant Files | OX did not detect supported files in the repository. |
In addition to the automatic app being made irrelevant by OX, the admin can manually mark the app as irrelevant.
To manually mark application (s) as irrelevant:
* On the **Applications** page, select the applications that you want to mark as irrelevant and select **Make Irrelevant**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ox.security/scan-and-analyze-with-ox/analyzing-scan-results/applications/managing-applications/irrelevant-applications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.