> 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/clarity-lims/instruments-and-integrations/other-release-notes/novaseq6k-file-v2.3.0-release-notes.md).

# NovaSeq 6000 File-based v2.3.0

The NovaSeq 6000 Integration v2.3 has the following compatibility:

* Clarity LIMS v4.2 or later, until v6.0. Not compatible with v6.0 or later.
* NGS Extensions Package v5.20 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 asymmetric sequencing read length.
* Support for reverse complement workflow in sample sheet generation.
* Support for Unique Molecular Identifiers (UMI) configuration that is populated in sample sheet.
* Updated preconfigured workflow (NovaSeq 6000 v2.1).
* Support SPrime (SP) flow cell in the preconfigured workflow.
* PhiX spike-in volume calculation script.
* Update to the latest flow cell barcode mask.
* New secret management mechanism.

## Defects Fixed

* Fixed the 'NULL' value for custom primer settings in JSON recipe issue.
* Fixed the lane number discrepancy issue in Automated - NovaSeq Run step.

## Known Issues

Minor bug in SecretUtil v1.0.0 that causes some NGS automation scripts to fail if the command does not have -l parameter. This will be fixed in the SecretUtil v1.0.1 release (Dec 2020). Until then, add "-l" in the automation script to bypass the bug i.e. bash -l -c "......". The automation scripts affected are:

* assignQC
* assignQCForDemuxStep
* parseBioAnalyzer
* parseCSV
* place\_samples\_by\_robot\_file
* parseXmlBySampleName


---

# 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/clarity-lims/instruments-and-integrations/other-release-notes/novaseq6k-file-v2.3.0-release-notes.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.