> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/troubleshooting/readme.md).

# Troubleshooting

Find what is wrong and fix it.

Paste the error message, or describe what you see. Our help center AI agent answers right away.

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question…</button>

<h2 align="center">Where did the error appear?</h2>

<p align="center"><mark style="color:$info;">A passing QC test means your BactoBox® works.</mark></p>

<figure><img src="https://1589625940-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQorx08wID6YNpw8pEV0j%2Fuploads%2F019y0PPVb2FlGbPF9yxU%2Fwhere-did-the-error-appear.svg?alt=media" alt="Error during a sample: clean and try again. If the error comes back, run a QC test. If the QC test passes, your BactoBox® works and the cause is in the sample. See Sample gives an error. If the QC test fails, follow the steps for your error code. See QC test fails. Error during a QC test: follow the steps for your error code. See QC test fails."><figcaption></figcaption></figure>

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-vial">:vial:</i> <strong>Sample gives an error</strong></td><td>An error while you measure your own sample.</td><td><a href="/troubleshooting/sample-gives-an-error.md">Sample gives an error</a></td></tr><tr><td><i class="fa-vial-circle-check">:vial-circle-check:</i> <strong>QC test fails</strong></td><td>The QC test shows an error or does not pass.</td><td><a href="/troubleshooting/qc-test-fails.md">QC test fails</a></td></tr><tr><td><i class="fa-list-ol">:list-ol:</i> <strong>Error codes</strong></td><td>Look up the code on your screen.</td><td><a href="/troubleshooting/error-codes.md">Error codes</a></td></tr><tr><td><i class="fa-screwdriver-wrench">:screwdriver-wrench:</i> <strong>Other problems</strong></td><td>Power, display, Access, software update and more.</td><td><a href="/troubleshooting/other-problems.md">Other problems</a></td></tr></tbody></table>

Still stuck? [Contact support](/troubleshooting/contact-support.md).


---

# 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://help.sbtinstruments.com/troubleshooting/readme.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.