> For the complete documentation index, see [llms.txt](https://docs.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaedim3d.com/managing-assets/asset-status.md).
# Asset Status
In the Assets page, you will be able to see real-time updates for all of your assets.
There are four stages:
### 1. Processing
A processing stage is a work in progress. This means that your request has been received and is going through the generation and quality check process.
### 2. For Review
Once your asset has finished processing, you will be able to review it. In the review stage, you can [request revisions](/reviewing-assets/request-revisions.md#request-revisions-for-prototype-assets), upload a new version, or approve the stage.
### 3. Completed
The "Completed" status indicates that an asset's stage has been approved or the asset has finished all the steps of the pipeline.
Once you've approved your asset, it will be marked "Approved" until you start processing the next step. After approval, the "Process \[Next step]" button will have a countdown. You can cancel this by clicking "Back," or skip the countdown by clicking on the button again. Otherwise, the next stage will be processed automatically.
If your asset has finished all the steps, you will have the option to create a new asset or Download the final asset.
### 4. Generation Failed
The "Failed" status indicates that your generation has been dismissed. The reason for dismissal will be displayed in one of the panels of your asset:
---
# 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.kaedim3d.com/managing-assets/asset-status.md?ask=&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.
