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

# Troubleshooting Fluidics Pre-Run Check Errors at 88% on the MiSeq i100 Series

**Background**

During the Pre-Run Checks, the instrument measures the average Illumination intensity after flowing buffer through the flow cell to ensure that the Optics and Fluidics systems are performing as expected.

If the average intensity values are outside of specification, the Pre-Run Checks stop during the Fluidics checks approximately 88% of the way through the check completion. If this issue occurs, please see the following Troubleshooting Actions.

**Troubleshooting Actions**

1. Cancel the Pre-Run Checks and exit the Run Setup.
2. Power cycle the instrument.
   1. See Knowledge Article [How to Power Cycle the MiSeq i100 Series](https://knowledge.illumina.com/instrumentation/miseq-i100-series/instrumentation-miseq-i100-series-reference_material-list/000009277.md) for additional details if needed.
3. Perform the instrument System Health Checks.
   1. See Knowledge Article [How to Setup the System Health Checks on the MiSeq i100 Series Instruments](https://knowledge.illumina.com/instrumentation/miseq-i100-series/instrumentation-miseq-i100-series-reference_material-list/000009206.md) for additional details if needed.
4. Collect the **Standard** Export Logs bundle.
   1. See Knowledge Article [How to Export Logs on the MiSeq i100 Series](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000009265.md) for additional details if needed.
5. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) to review the Pre-Run Check results and System Health Check report before proceeding with follow up sequencing run.

\
\
\ <br>

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