> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/orbit/en/help/faq/analyse-laeuft.md).

# Why is an archive in Analyzing…?

Why a software archive in powerIO Orbit is in Analyzing…, how long the analysis takes, and what helps with Not analyzed or Analysis failed.

The archive analysis is still running. It takes up to <code class="expression">space.vars.analysis\_max\_minutes</code> minutes, after which the result appears without reloading the page.

## If the analysis takes longer

If an analysis takes longer than <code class="expression">space.vars.analysis\_max\_minutes</code> minutes, Orbit offers it again. Click on the archive status to restart the analysis. The roles are allowed to do that **Customer admin**, **Project admin** and **Project manager**.

## Other analysis states

| Status              | Cause                                                                           | Solution                                                                                                |
| ------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Not analysed**    | The analysis was disabled during upload, or the archive comes from before then. | The **Customer admin** starts the analysis under **Settings** > **Analysis** with **Analyze them now**. |
| **Analysis failed** | Orbit was unable to read the values from the archive.                           | Click on the status to try again.                                                                       |

More about the analysis can be found at [powerIO Orbit: Upload software archive](/hub/orbit/en/projects/projekte/softwarearchiv-hochladen.md) and [powerIO Orbit: Organization settings](/hub/orbit/en/administration/einstellungen.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.powerio.com/hub/orbit/en/help/faq/analyse-laeuft.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 `build a script that syncs our docs to a CMS` 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.