> 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/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000005855.md).

# Best practices for NextSeq 500/550 pre-run check failures requiring a power cycle

**Note:** A mitigation has been implemented in NCS v4.2 which prevents the consumables from being marked as used if they do remain in the instrument during a power cycle.

For instruments operating on a Control Software version older than v4.2, the workflow still advises to **remove all consumables** prior to power cycling the instrument.

Some pre-run check failures will require a power cycle for resolution. In these instances, **remove the consumables** from the instrument **prior to power cycling**. To remove the consumables prior to power cycling, complete the steps listed below:

1. Navigate to the Home Screen.
2. Select **Manage Instrument**.
3. Select **Unload Consumable**.
4. Remove all Consumables.
5. Perform a Power Cycle. Reference article of [How to Power Cycle the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001972.md).

* This is best practice for any NextSeq 500/550 instruments (all NextSeq Control Software (NCS) versions) to prevent issues in detecting consumables.

\
\
\ <br>

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