> 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/miseq-ruo/instrumentation-miseq-ruo-troubleshooting-list/000002083.md).

# Troubleshooting MiSeq washes taking extended time to complete

If a MiSeq wash is taking longer than expected to complete, the instrument may have encountered a communication error, causing the wash to stall.

**To Troubleshoot:**

1. Confirm which wash was intended and when it was started. Verify that the wash has been running longer than expected for that wash type. See more details in [Best Practices for Washes on the MiSeq](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001679.md).
   * Post-run wash: 20 minutes or 30 minutes, if using the template line wash option.
   * Maintenance wash: 90 minutes (three steps - 30 minutes each step).
   * Standby wash: 120 minutes (two steps - 60 minutes each step).
2. If the wash is stalled, power cycle the MiSeq following the intructions in [How to Power Cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md).
   * If the MiSeq Control Software (MCS) is responsive, exit the wash and shut down the MiSeq.
   * If the MCS is not responsive, open the task manager to end the task for MCS via the following pathway: Task Manager > Processes > MiSeqSoftware.exe > End Task.
     * Open the task manager by right-clicking in the taskbar and select task manager or by pressing CTRL +ALT+DEL and select task manager.
   * Shut down MiSeq through the Windows start menu, and toggle the power switch at the back of the instrument to the OFF position. Leave powered down for a full minute.
3. After turning the instrument back on, if the instrument initializes without errors, repeat the wash that was in progress and monitor the time to complete.
4. If there are errors during system re-initialization or if the wash gets stalled again, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) for further assistance.

\
\
\ <br>

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