# How to troubleshoot MiSeq runs taking longer than usual or expected

Expected run times on the MiSeq vary between 5.6-62.3 hours. Run time is dependent on the run length, kit type used, and whether the run is single-end or paired-end. A full list of run time estimates can be found in the Illumina Knowledge Article [Run time estimates for each sequencing step on Illumina sequencing platforms](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001540). However, users may experience runs taking longer than expected. This may occur for a variety of reasons. In order to troubleshoot longer than expected run time, review the following settings on the instrument:

**On Instrument Root Causes**

* Determine the amount of free disk space on the C:\ and D:\ drives. Files in the Recycle Bin are still included in space calculation. The Recycle Bin needs to be emptied to fully allocate free space. Lower amounts of free disk space on the C:\ and D:\ drives may lead to reduced run speed.
* If saving runs locally, consider moving off-instrument to long-term storage. It is recommended to move old run folders from the MiSeqAnalysis and MiSeqOutput folders to long-term storage regularly to maintain free disk space on the instrument.
* Extended run times may occur if the instrument is not power cycled regularly.

To troubleshoot, power cycle prior to sequencing run, clear the hard disk drive (HDD) and monitor the run time of subsequent runs. Information on steps to Power Cycle the MiSeq can be found in the Illumina Knowledge Article [How to shut down or power cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-reference_material-list/000001894).

**Off Instrument Root Causes**

* Transient internet or network issues may also contribute to run time slowness. When Illumina Proactive is enabled, delays at the end of runs may occur if internet or network issues occurred during the run.
* Changes to the network environment, group policy objects (GPOs), or antivirus (AV) updates occurred during the time that run slowness was observed.

If review of the above does not resolve the extended run times and the issue is persistent, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for continued troubleshooting.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6023), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006023%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions: 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:

```
GET https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000006023.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.