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

# Troubleshooting Timeout waiting 60000 ms within event EventToBlockingConverter error on the MiniSeq

**Cause**

This error occurs due to a communication issue with a component on the MiniSeq.

**Troubleshooting steps**

1. Select the error in the MiniSeq Control Software to determine which component had the error. It is listed as "Command "XXXX" reported X exception(s)."
2. Power cycle the instrument.
   * For further information, see article [How to Power Cycle the MiniSeq](https://knowledge.illumina.com/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002010.md).
3. If the instrument initializes normally and there have been no other communication errors on the instrument within the last month, set up the next run and monitor for similar issues.
4. If the instrument fails to initialize or a similar error occurs, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).

**Example image of error:**

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-b9e5a78f6e9d2c563f1c101a8dca49b9f09d64c8%2Fimage1.jpg?alt=media\&token=a10e2365-b4ed-452b-9ced-2920d95d3cb0)

\
\
\ <br>

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