> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-faq-list/000006211.md).

# What do NovaSeq 6000 status bar colors mean?

The NovaSeq 6000 instrument includes a light-emitting diode (LED) status bar beneath the flow cell compartment. The status bar provides an at-a-glance indication of the instrument state.

* **Green**: ready to sequence
* **Blue**: processing
* **Orange**: needs attention

  ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-4b0d26f47f412bd905204046f48015c4bbf2cf5a%2Fimage1.jpg?alt=media\&token=a927cfd8-db22-4aa4-92f6-43fb4de012c4)

Other colors not mentioned here, such as white or pink, do not correspond to an instrument status. If seen, Illumina Technical Support recommends a power cycle of the instrument to reset communication for the LED status bar.

* For further information, search for Knowledge Base article [How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md) or [How To Power Cycle NovaSeq 6000 Video](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000005611.md).

More information, reference [NovaSeq 6000 Sequencing System Guide](https://support.illumina.com/downloads/novaseq-6000-system-guide-1000000019358.html).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6211), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006211%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-faq-list/000006211.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.
