> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/instruments/sample-details.md).

# Sample details

Click a sample on a storage account's samples page to open its **sample details** page. It gathers the sample's metadata, its files, and the workflow runs that analyzed it.

## Custom attributes

If custom attributes have been uploaded for the sample (see [Adding sample metadata](/products/workbench/instruments/adding-sample-metadata.md#custom-attributes)), a **Custom attributes** card shows them in a read-only JSON viewer.

* **Copy** copies the attributes to your clipboard as JSON.
* **Clear all** removes every custom attribute from the sample. Confirm in the **Clear custom attributes** dialog. This needs the **Manage Samples** capability.

Attributes can't be edited on this page. To change them, upload the metadata file for the sample again.

{% hint style="warning" %}
Clearing custom attributes can't be undone. To restore them, upload the sample's metadata file again.
{% endhint %}

## Analysis and ingestion progress

The **Analysis** section lists the workflow runs for the sample. Expand a run to see its details.

For runs that load variants into the [Variant Interpreter](/products/workbench/variant-interpreter.md), the expanded run shows an ingestion tracker with three steps:

1. **Data Ingestion**: the ingest workflow reads the run's outputs.
2. **Data Registration**: the ingested files are registered with Workbench.
3. **Data Indexing**: the registered data is indexed so it can be queried.

Each step shows whether it's pending, in progress, complete, or failed. Steps after a failure are marked as not run. Hover over a step for details.

If only some files registered, the step shows **Partly registered** with a count, for example "Partly registered — 18 of 20". **Review analysis** stays available once some data has registered, even while a later step is still pending.

### Investigating a failure

On a failed or partly completed step:

* **View error detail** (Data Registration and Data Indexing) lists each file that didn't register or index, with its full path and the reason. Use **Copy Error** to copy the details, for example to send to your administrator.
* **View error logs** opens the run's logs on the Monitor page.

### Retrying or stopping ingestion

You can recover from a failed step without starting over:

| Situation                                    | Action                                         | What it does                                                                                               |
| -------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Data Registration failed or partly completed | **Retry registration**                         | Re-registers the already-ingested data. This usually takes seconds.                                        |
| Data Registration failed or partly completed | **Re-run from ingestion instead**              | Re-runs the whole ingest workflow, not just registration. Confirm in the **Re-run from ingestion** dialog. |
| Data Indexing failed                         | **Retry indexing**                             | Retries indexing for the files that didn't reach the index.                                                |
| Data Ingestion failed                        | **Retry ingestion**                            | Re-runs the ingest workflow from the start.                                                                |
| A step is running                            | **Stop** (for example **Stop data ingestion**) | Marks the step failed. You can retry it afterwards from wherever it stopped.                               |

If a retry can't be started, the reason is shown below the buttons.


---

# 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.omics.ai/products/workbench/instruments/sample-details.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.