> 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/nextseq-500-550/instrumentation-nextseq-500-550-faq-list.md).

# FAQ

Instrumentation > NextSeq 500/550 > FAQ

* [At which cycle of NextSeq 500/550 are run metrics calculated?](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000002584.md)
* [Can the output folder for a NextSeq 500/550 run be saved to the local computer?](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000005512.md)
* [Common questions regarding custom recipes for the NextSeq 500/550](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000002618.md)
* [Do NextSeq 500/550 v2.5 runs have different specifications than v2.0 reagent runs?](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000002609.md)
* [Does the NextSeq 500/550 Control Software prevent run setup with read lengths smaller than 25 cycles?](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000002565.md)
* [How to set up a NextSeq 500/550 to upload to a BaseSpace Enterprise account using NCS v4.2](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000005913.md)
* [What do the NextSeq 500/550 status bar colors mean?](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000006206.md)
* [What is the maximum read length supported in one direction on a NextSeq 500/550 run?](/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-faq-list/000002588.md)


---

# 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/nextseq-500-550/instrumentation-nextseq-500-550-faq-list.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.