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

# Troubleshooting Z motor errors occurring mid-run on the MiSeq

A Z-motor error occurring mid-run can be caused by instrument fluidics, debris, smudges on the flow cell, or library overclustering issues.

**ERROR:** "While trying to find focus, the Z stage has attempted to move outside its acceptable range."

**Troubleshooting steps:**

1. Confirm reagent kits were not expired at the time of the run.
2. Confirm the quality and quantification of the library were as expected and were checked in accordance with Illumina-recommended methods.
3. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) with the following run files to review the library performance.
   1. From within D:\Illumina\MiSeqTemp\&lt;run folder>, send:\
      InterOp folder\
      RunParameters.xml\
      RunInfo.xml\
      Thumbnail\_Images\L001\C1.1 (cycle 1)\*\
      \*Send cycles 1-10 and the last 10 cycles before the run failed.
4. Power cycle\* the instrument. Reference[How to Power Cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md). This information is also available in video form. Refernce article [How To Power Cycle the MiSeq Video](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md).
5. If the instrument initializes successfully, perform a System Check on the instrument. Reference [How to perform a System Check on the MiSeq](https://github.com/illumina-swi/illumina-knowledge/tree/master/docs/Instrumentation/MiniSeq/Reference_Material/000001777.md).
6. If the system check passes and Technical Support does not suspect a library-related issue, proceed with setting up the next run.
7. If Z-motor error recurs in the subsequent run, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/).

\
\
\ <br>

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