> 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-reference_material-list/000001448.md).

# Wash Notifications on the MiSeq

The following notification in MiSeq Control Software 2.6.2.1 or below does not impact run performance if washes are performed on their required schedule. This notification has been resolved in MiSeq Control Software 3.1 and later versions.

**Notification**: "It has been 7 or more days since the instrument fluidics were last used."

**Troubleshooting Steps**:

1. Make sure that the **DONE** button is selected at the end of each wash to log the wash in the system.
2. Confirm the date, time, and time zone on the instrument are correct.
3. Confirm region and language are set to *English* (if in the United States)*.*
4. [Power cycle](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) the instrument.
5. If the instrument still prompts for a wash, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) for further assistance.

For further information, search for the following knowledge base articles:

* [**Wash Notifications on the MiSeq**](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001448.md)
* [**How To Power Cycle the MiSeq Video**](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md)
* [**How To Power Cycle the MiSeq Video**](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md)

\
\
\ <br>

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