> For the complete documentation index, see [llms.txt](https://documentation.panomics.bio/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.panomics.bio/documentation/samples/sample-lifecycle.md).

# Sample Lifecycle

Samples in Panomics have a predefined lifecycle.

<figure><img src="/files/yxnlgcEE8Rzx5lQJr1Cl" alt=""><figcaption><p>Sample lifecycle</p></figcaption></figure>

<table><thead><tr><th width="184">Status</th><th>Description</th></tr></thead><tbody><tr><td>DRAFT</td><td>This is the initial status for each sample that gets imported in Panomics. Samples stay in the <code>DRAFT</code> status until they are sent to the <code>Standard Compute</code> runtime for loading.</td></tr><tr><td>LOADING</td><td>Samples get processed by the <code>Standard Compute</code> runtime. During this time, the samples have the <code>LOADING</code> status. </td></tr><tr><td>ANNOTATING</td><td>This is a checkpoint status, meaning that transitioning away from <code>ANNOTATING</code> requires the "mark as ready" user action. While in this status, sample metadata can be applied either by uploading a file or by editing the metadata fields through the UI.</td></tr><tr><td>SAVING</td><td>When marked as ready, sample data is merged with the metadata via the <code>Standard Compute</code> runtime. </td></tr><tr><td>READY</td><td>Once the metadata is successfully merged with the sample data, samples transition to the <code>READY</code> state and can be used to create analyses. Ready samples can be transitioned back to the <code>ANNOTATING</code> state by users via the "mark as annotating" action.</td></tr><tr><td>FAILED</td><td>Any failure during the loading or saving processes transitions the sample to the <code>FAILED</code> status. Failed samples can only be deleted.</td></tr></tbody></table>


---

# 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://documentation.panomics.bio/documentation/samples/sample-lifecycle.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.