> For the complete documentation index, see [llms.txt](https://help.claritylims.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.claritylims.illumina.com/instruments-and-integrations/other-release-notes/novaseq6k-api-v3.2.2-release-notes.md).

# NovaSeq 6000 API-based v3.2.2

## Compatibility

* Clarity LIMS v4.2 to v5.3. Not compatible with v5.4 or later.
* NGS Extensions Package v5.19. Not compatible with v5.20 or later.
* Preconfigured Workflow Package (PCWP) v1.2.2. Not compatible with v2.0 or later.
* NovaSeq Control Software (NVCS) v1.7.0.
* Illumina Bcl2FastQ v2.20.

## Features to Note for this Release

This release of Clarity LIMS integration package provides:

* Support for the NovaSeq Control Software v1.7.0 with v1.5 reagents.
* Support for reverse complement workflow in sample sheet generation.
* Support for Unique Molecular Identifiers (UMI) configuration that is populated in sample sheet.
* Updated workflow (NovaSeq 6000 v3.0.1) delivered directly from PCWP v1.2.2.

## Defects Fixed

* Fixed lane number discrepancy issue in Automated - NovaSeq Run step.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.claritylims.illumina.com/instruments-and-integrations/other-release-notes/novaseq6k-api-v3.2.2-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.