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

# Troubleshooting "Error in Fluidics, LanePump" errors on the MiniSeq

**Background**

When performing sequencing runs or washes on the MiniSeq, users may encounter the following run/wash-stopping error:

* Error in Fluidics. FlowCellFluidics1.LanePump.1xPassThroughRheodyneValve1:Exceeded retries:Originally caused by:Timeout waiting 60000ms within EventToBlockingConverter.WaitforData

This error may sometimes be accompanied by the following errors:

* Error in Fluidics. FlowCellFluidics1. LanePump.1XPassThroughCavroSyringePump1. Auto syringe overload recovery for dispense is not enabled.
* Error in Fluidics. FlowCellFluidics1.LanePump.1xPassThroughRheodyneValve1:Exceeded retries:

These errors may be caused by communication issues onboard the instrument or fluidics related issues.

**Troubleshooting steps:**

1. Power cycle the instrument.
   * For further information, see Illumina Knowledge Article [How to Power Cycle the MiniSeq](/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002010.md).
2. Perform a Fluidics check on the instrument from the System Check menu.
   * For further information, see Illumina Knowledge Article [How to Perform a System Check on the MiniSeq](/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002040.md).
3. If the instrument initializes successfully and the fluidics check passes, proceed with setting up the next sequencing run.
4. If the instrument does not initialize or any of the fluidics tests fail, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for the next steps.

\
\
\ <br>

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.illumina.com/instrumentation/miniseq/instrumentation-miniseq-troubleshooting-list/000007120.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.