> 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/000009121.md).

# Troubleshooting Reagent Compartment Doors Failing to Unlock on the NovaSeq X Series

**Background**

The reagent compartment doors on the NovaSeq X Series are operated through the Control Software. Users may find the reagent compartment doors fail to unlock automatically or require physical assistance to fully open. In such situations, please follow the steps below to resolve issues with reagent doors not unlocking:

1. This command may take several minutes between selecting the **Unlock Doors** command and the doors opening. The first step is to wait and see if the doors unlock after a delay.
2. If the doors remain locked, cancel the command via the Control Software and then select the **Unlock Doors** button again to retry.
3. If the doors remain locked, proceed to power cycle the instrument and then attempt to unlock the reagent doors after complete power cycle and initialization.
   1. Instructions for power cycling the NovaSeq X Series are available here: [How to Power Cycle the NovaSeq X Series Instruments](https://knowledge.illumina.com/instrumentation/novaseq-x-x-plus/instrumentation-novaseq-x-x-plus-reference_material-list/000007478.md).
4. If the doors remain locked after following these steps, 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 #9121), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000009121%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/000009121.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.
