> 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/general/instrumentation-general-troubleshooting-list/000001689.md).

# How to troubleshoot spent reagent cartridge not detected on NextSeq 500/550

**Background**

The NextSeq 500/550 instruments divert used reagents to the spent reagents cartridge for storage until the user empties it after sequencing runs complete. If the spent reagents cartridge is not detected, the Control Software will alert the user with the *Unable to detect spent reagent cartridge* error on the NextSeq 500/550. This error appears when:

* The instrument does not register the spent reagent cartridge during pre-run checks
* The instrument fails to detect the spent reagent cartridge is present while setting up a wash or a sequencing run
* The instrument registers there is a spent reagent cartridge inserted even when it is taken out

If receiving a “spent reagents cartridge is full” related error, please see article: [Troubleshooting spent reagent cartridge is full on the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-troubleshooting-list/000001392.md).

**Troubleshooting Actions**

1. Power cycle the instrument to reset the sensor communications.
   1. From the instrument home screen, select **Manage Instrument**.
   2. Select **System Shut down Options**.
   3. Select **Shut Down** (this will shut down software and turn off instrument power).
   4. Wait two minutes before turning on the instrument from the button in front.
2. If the error message continues to appear, contact [Illumina Technical Support](https://sapac.illumina.com/company/contact-us.html) to determine the next steps.

\
\
\ <br>

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