> 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/novaseq-6000/instrumentation-novaseq-6000-faq-list/000002324.md).

# When can runs be staggered on NovaSeq 6000?

**Background**

On the NovaSeq 6000, a run can be set up and started on the idle side of the instrument while a run is in progress on the other side. This is referred to as a **staggered start**.

Staggered runs are set up at specific times during the run on the other side, as indicated by the following start countdown timer states, which are displayed on the instrument.

* **Run Start: Available**
  * Staggered start is available.
  * The date and time show when staggered start will become available.
  * Select **Sequence** to start a new staggered run after the current cycle is complete.
* **Run Start: Unavailable**
  * Staggered start is unavailable.
  * The date and time show when staggered start will be available on the other side of the instrument.
* **Waiting...**
  * If a new run is attempted when staggered start is unavailable, the state changes to Waiting... and the date and time show the approximate time that the instrument will be ready for the new run.
  * The instrument proceeds to run setup when staggered start is available.

When setting up the new run, the software automatically pauses and resumes the run on the adjacent flow cell as needed. The system is placed in a safe state when paused.

**Procedure**

1. From the home screen, select **Sequence**, and then select **A** or **B**.
   * The selected side must be the currently idle side.
2. Wait for the run on the adjacent flow cell to pause. To cancel the new run and prevent pausing, select **Cancel**.
   * If the adjacent run is performing cluster generation, paired-end resynthesis, imaging, or washing, the software completes the current step before pausing.
3. When the adjacent run is paused and the flow cell door opens, set up the new run.

See the Staggered Start of Runs section of [NovaSeq 6000 Sequencing System Guide](https://support.illumina.com/downloads/novaseq-6000-system-guide-1000000019358.html) for more information.

\
\
\ <br>

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