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

# Troubleshooting "An unexpected error occurred during sequencing" Errors on the MiSeq i100 Series

**Background**

Issues during a sequencing run that the Control Software is not able to categorize will stop the run and present the following generic error message in the Notifications menu:

"An unexpected error occurred during sequencing."

If this issue presents during a sequencing run, please see the following Troubleshooting Actions.

**Troubleshooting Actions**

1. Select **Eject Cartridge**, to remove the dry and wet sequencing cartridges from the instrument.
2. Run the instrument **System Health Checks** using the Test Cartridges provided with the instrument.
   1. See Knowledge Article [How to Setup the System 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 more information.
3. Once the System Health Checks are complete, select **Clear Checks** and then proceed to the Control Software home screen.
4. Open the menu and select **Settings**. Then select **Export Logs**
   1. Select the **Standard** option to bundle the System Health Check results.
   2. Select the **affected Sequencing Run** from the list when setting up the Export Logs.
   3. 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 more information.
5. Once these actions are completed, contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html) for next steps.

\
\
\ <br>

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