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

# Status reference

Status words describe different layers. A task can be Running while one deployment is Failed, or a transaction can be Confirmed while market data is still Syncing.

## Data display states

| Display              | Meaning                                                                |
| -------------------- | ---------------------------------------------------------------------- |
| Loading / Syncing    | The request has not finished.                                          |
| `0` / No results     | The request succeeded and returned a real zero or empty result.        |
| Unavailable          | The value or capability cannot currently be provided.                  |
| Stale / Reconnecting | Existing data is retained while a refresh or live connection recovers. |

KK.one keeps loading, real zero, and unavailable states distinct.

## Task states

| State            | Meaning                                                                         |
| ---------------- | ------------------------------------------------------------------------------- |
| Draft            | Task setup is saved but not running.                                            |
| Running          | Monitoring and future qualifying actions are active.                            |
| Paused           | Future task processing is paused.                                               |
| Partially active | At least one selected live network can run and another is persistently blocked. |
| Needs funding    | The task has no currently usable selected network capacity.                     |
| Completed        | The configured task cap has been reached.                                       |

## Launch result states

| State          | Meaning                                                                        |
| -------------- | ------------------------------------------------------------------------------ |
| Detected       | A candidate narrative was identified.                                          |
| Skipped        | A saved rule excluded the candidate.                                           |
| Preparing      | Metadata, funding, network, or transaction data is being prepared.             |
| Submitted      | The network action was sent but is not yet final.                              |
| Confirming     | Waiting for sufficient network confirmation.                                   |
| Confirmed      | The network confirmed the deployment.                                          |
| Indexing       | The token exists but market or search data is still synchronizing.             |
| Failed         | The current attempt is known not to have completed successfully.               |
| Partial launch | One launch group contains both confirmed and unsuccessful network deployments. |
| Unknown        | KK.one cannot yet determine the final network outcome.                         |

## Send, Claim, Trade, and Auto Sell transaction states

Typical progression:

`Ready → Review → Waiting for authorization → Submitting → Confirming → Confirmed`

An action can instead become Failed, Rejected, Expired, or Unknown. After submission, closing a modal or page does not cancel the network transaction.

## Claim states

* **No rewards** — successful query, nothing claimable.
* **Ready** — claimable amount and required context are available.
* **Insufficient fee** — the paying wallet lacks the required network fee asset.
* **Waiting for authorization** — a signature or approved permission is required.
* **Pending / confirming** — final network result unresolved.
* **Confirmed** — claim confirmed.
* **Failed** — claim attempt failed and may be retryable if marked safe.


---

# 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://kkone.gitbook.io/kkone-docs/reference/status-reference.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.