> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/basespace/releases/previous-releases/2017/5.2.0.md).

# 5.2.0

### August 24, 2017 - 5.2 - Increased Number of Library Kits Listed in the Library Prep Chooser

* Features
  * Increased the limit on the number of library prep kits displayed in the Prep Tab Library Prep Kit chooser
* Bugs Fixed
  * Fixed a display issue with the project filter dropdown on the file chooser screen
  * Fixed links to run files lists
  * Fixed the checkboxes in the Prep Tab samples list to display only for biosamples created in Prep Tab

### Release 5.2.1 - August 29, 2017 - Staged roll out in completed

* FASTQ Generation
  * Added support for NovaSeq S4 flow cell


---

# 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://help.bioinsight.illumina.com/basespace/releases/previous-releases/2017/5.2.0.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.
