> For the complete documentation index, see [llms.txt](https://nvsbl.gitbook.io/apphafen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nvsbl.gitbook.io/apphafen/statuses.md).

# Statuses

This app shows two kinds of status information for products:

* a normalized status pill
* a check info tooltip

The UI is designed so the visible label stays compact while the exact store wording stays available on hover.

## What the status pill means

The pill shows the app's normalized interpretation of the current store state.

Examples:

* `Draft`
* `Ready To Submit`
* `Submitted For Review`
* `In Review`
* `Approved Pending Release`
* `Live`
* `Rejected`
* `Removed By Developer`
* `Removed By Store`
* `Unknown`

These labels are meant to stay consistent across providers so you can scan mixed Apple, Chrome, and Mozilla products quickly.

## What the pill tooltip means

Hover the pill to see the exact provider-side status returned by the store.

Examples by provider:

### Apple

The tooltip can show values such as:

* `PREPARE_FOR_SUBMISSION`
* `WAITING_FOR_REVIEW`
* `IN_REVIEW`
* `PENDING_DEVELOPER_RELEASE`
* `READY_FOR_SALE`
* `REJECTED`
* `REMOVED_FROM_SALE`

### Chrome Web Store

The tooltip can show values such as:

* `PENDING_REVIEW`
* `STAGED`
* `PUBLISHED`
* `PUBLISHED_TO_TESTERS`
* `REJECTED`
* `CANCELLED`
* `TAKEN_DOWN`

### Mozilla AMO

The tooltip can show a compact combined AMO state such as:

* `public / listed / public`
* `public / unlisted / public`
* `nominated / listed / unreviewed`
* `incomplete`
* `disabled`
* `deleted`
* `rejected`

For Mozilla, the combined value helps show both the add-on state and the version/channel context.

## What the info tooltip means

Hover the small `i` icon next to a product status to see check details.

This tooltip can include:

* whether checks are automatic
* whether a check is queued or currently running
* the last successful check timestamp
* the next queued check time when one already exists
* an estimated next automatic check time when no queued run is visible
* the latest failure or rate-limit issue when one exists

Examples:

```
Status checks run automatically
Last checked: 2026-05-04 13:10:00
Next scheduled check: Around 2026-05-04 14:10:00
```

```
Delayed by provider rate limits
Last checked: 2026-05-04 12:55:00
Next scheduled check: Around 2026-05-04 13:55:00
Latest issue: Chrome API rate limit reached.
```

```
Connection needs attention
Last checked: Never
Next scheduled check: Blocked until the connection is fixed
```

## How the next check is determined

The app shows the next check time using this order:

1. A real queued check time if a product check job is already pending.
2. A simple estimate from the last check timestamp plus the configured product sync interval.
3. A fallback message when the app has not checked the product yet or cannot calculate a time.

By default, recurring product checks are scheduled about every 60 minutes, with some jitter for normal background work.

## Where you see this UI

The normalized pill and check info tooltip are used in:

* the Products list
* the product detail page
* dashboard attention items

Version rows on the product detail page also use normalized pills with the exact provider version status in the tooltip.


---

# 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://nvsbl.gitbook.io/apphafen/statuses.md?ask=<question>&goal=<endgoal>
```

`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.