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

# Troubleshooting

Instrumentation > MiSeq > Troubleshooting

* [Troubleshooting "@@@--- Failed to get temperature" error on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001453.md)
* [Troubleshooting "Compensator Move and/or Sensor Failed" errors on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000008020.md)
* [Troubleshooting "Conflict" errors at the end of MiSeq runs](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000008345.md)
* [Troubleshooting "Initialize Cameras before capturing images" error on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000007442.md)
* [Troubleshooting "Primary Analysis Not Ready" errors during Pre-run Checks on MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000003755.md)
* [Troubleshooting "TEC2SERVO unrecognize char" error during MiSeq Control Software initialization](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000002865.md)
* [Troubleshooting "Unable to communicate with BaseSpace" error when setting up MiSeq run on Windows 10](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000007849.md)
* [Troubleshooting "Unsuccessfully attempted to launch module type" error with LRM v3 on MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000003872.md)
* [Troubleshooting "Y home sensor never tripped" error on MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000002353.md)
* [Troubleshooting "file is not properly formatted" warning on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000009180.md)
* [Troubleshooting 'Index outside the bounds of the array' error on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001432.md)
* [Troubleshooting FPGA RFID ERROR STATUS 2 errors on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001909.md)
* [Troubleshooting Invalid Role Errors after Post-Run Washes on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000009173.md)
* [Troubleshooting MiSeq "Z Motor The Z stage amp Op-amp might not be wired correctly" Error](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001913.md)
* [Troubleshooting MiSeqOverride.cfg Errors on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000003299.md)
* [Troubleshooting Network Connection Active errors during Pre-run Checks on MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000003754.md)
* [Troubleshooting RFID Not Recognized Error on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001459.md)
* [Troubleshooting Sipdown Errors on the MiSeq video](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000006824.md)
* [Troubleshooting Stalled Flow Rate Check on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000009288.md)
* [Troubleshooting Z Motor Positive soft limit too nonlinear at innermost test point on the MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000002241.md)
* [Troubleshooting no intensity for index read on MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001461.md)
* [Troubleshooting scratched or damaged flow cells on MiSeq](/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000003192.md)


---

# 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/instrumentation-miseq-troubleshooting-list.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.