> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/app-review/review-status.md).

# Review status

You can check the status of your custom app review in the **App flow** tab. The **App flow** tab describes all stages of your app: **Private**, **Published (approval not requested)**, **Published (pending approval)**, and **Approved**. When you click the **App flow** tab, your browser automatically scrolls and highlights the current stage of your app.

<figure><img src="https://1562974717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS0mCBwODiYtOVXjc6qf%2Fuploads%2Fgit-blob-7f7e94fd9860d298bbfbbc996e6483d70561e8bd%2Freviewstatus.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

When you request an app review, your app moves to the **Pending approval** stage.

{% hint style="info" %}
While the review request is received or in progress, avoid significant changes to the code of your app. They may slow down the review process.
{% endhint %}

If you have published your app or requested a review for a new app or an app update, you will see the **Review** tab. You can check the **Review Status** section at the bottom of the **Review** tab to see all activity that happened during the review.

<figure><img src="https://1562974717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS0mCBwODiYtOVXjc6qf%2Fuploads%2Fgit-blob-8a6ce6d2e378bfbd3486c87c1ff34576aeadabc9%2Freviewstatusactivity.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Every entry contains 4 columns:

* **Date and Time** - When the activity happened.
* **Action** - Name of the activity.
* **Status** - Available only with the action "Review status updated". The status of the app's review.
* **Comment (manual)** - A comment with additional information or context.

Possible actions are:

| Action                  | Explanation                                                                                |
| ----------------------- | ------------------------------------------------------------------------------------------ |
| App has been published. | You have published the app with the **Publish** button.                                    |
| Approval requested.     | You have submitted the review form. This action marks the start of the app review process. |
| Review form updated.    | You have updated the review form.                                                          |
| Review status updated.  | Make updated the review status.                                                            |
| App has been approved.  | Make approved your app. You app is now available to every user in Make.                    |

{% hint style="info" %}
You can also check your app review status in your email. The email has the subject: "*App review: YourAppName*". Make keeps all communication about the app review in this email thread.
{% endhint %}


---

# 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://developers.make.com/custom-apps-documentation/app-review/review-status.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.
