> 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/general/instrumentation-general-reference_material-list/000001540.md).
# Run time estimates for each sequencing step on Illumina sequencing platforms
The run time specifications for Illumina sequencing runs include cluster generation, SBS chemistry cycles, paired-end chemistry, and wash steps. In addition, runs that use non-patterned flow cells pause for a template building step. To aid in planning sequencing workflows and in estimating overall run times, Table 1 summarizes the estimated length of each sequencing step for Illumina sequencing platforms and chemistry versions.
**Table 1.** Approximate times for each sequencing step per instrument and supported chemistry
\* Template building time will vary based on cluster density\
\*\*Purge time varies based on the number of cycles\
\*\*\* XP workflow is approximately 150 minutes as ExAmp step is skipped
**Note:** Estimated run times will depend on cluster density and available computer resources. If the hard drive does not have sufficient space for data processing, or network location speeds are slow, run times may be increased. Total run times for the maximum read lengths of Illumina platforms, and other sequencing run specifications, can be found on the [Illumina Sequencing Platforms](https://www.illumina.com/systems/sequencing-platforms.html) web page.
NovaSeq X Control Software v1.4 introduces staggered run setup. Runs set up with differing flow cell types on either side may have longer run times expected. Information can be found in the [NovaSeq X Control Software v1.4 Software Release Notes](https://support.illumina.com/sequencing/sequencing_instruments/novaseq-x-novaseq-x-plus/documentation.html)
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1540), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001540%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/general/instrumentation-general-reference_material-list/000001540.md?ask=&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.