> 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-faq-list/000007999.md).

# When are the run folders created after initiating a sequencing run on the NovaSeq X/X Plus?

**Control computer Run folder (`/usr/local/illumina/runs/[RunID]`\*\*\*\*)**

The Run folder on the control computer is generated at the start of the run shortly after the pre-run checks complete.

**Compute engine Run folder (`/usr/local/illumina/mnt/runs/[RunID]`)**

The Run folder on the compute engine (CE) is not generated until after onboard cluster generation (OBCG) completes, which is approximately 4 hours after the run starts.\
The timing of OBCG depends on the type of flow cell being used, each of which are listed in [Run time estimates for each sequencing step on Illumina sequencing platforms](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001540.md).

**Network output Run folder**

The Universal Copy Service (UCS) software will create the run folder in the network output location and start the data copy after onboard cluster generation (OBCG) completes. There is an approximate 4 hour delay from when the run starts to when data copy begins.

\
\
\ <br>

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