> 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-troubleshooting-list/000001302.md).

# How to troubleshoot Reagent Selector Valve Errors on the NovaSeq 6000

Reagent Selector Valve errors can result from either a transient instrument communication issue or an instrument hardware related issue.

* Run stopping error messages:
  * "The software has exceeded three attempts to correct a problem with the reagent selector valve and cannot save the flow cell. Call Technical Support for help."
  * "The software has exceeded three attempts to correct a problem with the reagent selector valve and must end the sequencing run. Call Technical Support for help."

**To troubleshoot this type of error:**

1. Power cycle the instrument. For more information on power cycling, see the Knowledge Base article[How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md).
2. After the power cycle, perform **only** Valve Control test under Fluidics system check **five times.**
   1. Follow the steps outlined in [How to perform system checks on the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002495.md)
   2. Under Fluidics system checks, select Valve Control test only.
   3. Perform the test **five** times.
3. If any of the five system checks **fail**, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) and provide the system check results for further guidance.
4. If all tests **pass**, perform a wash and monitor for any valve error on the next run.
5. If the next run fails with the same error, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1302), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001302%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-troubleshooting-list/000001302.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.
