> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/clarity-lims/instruments-and-integrations/novaseq-x-series/novaseqx/novaseqx-v1.2.0/novaseqx-v1.2.0-release-notes.md).

# Release Notes

Last Updated: December 2024

Release Date: February 2024

Document Version: 3

These release notes describe the key changes to software components for the Clarity LIMS NovaSeq X Series Integration Package v1.2.0.

## Compatibility

Refer to [Compatibility](/clarity-lims/instruments-and-integrations/compatibility.md#novaseq-x-series) under Instruments & Integrations.

## New Features

* Supports analysis tracking at the metaworkflow level for analysis status and high level analysis summary results.
* Supports the new 1.5B and 25B flow cell types. The B3 flow cell has been renamed to the 10B flow cell.
* Uses the SecureString type for improving the security of values stored in the AWS param store.
* Includes the following improvements to the NovaSeq X Series Sequencing v1.1 protocol:
  * Removes the unused Output Folder step custom field from the Load to Library Tube Strip step.
  * Renames the Library Tube barcode step custom field to Library Tube Strip Barcode in the AUTOMATED - Sequencing Run step.

## Defects Fixed

* None

## Known Limitations

* The analysis step tracks only the first run, but not subsequent queued runs.
* The Local run mode does not support custom library prep and index adapter kits.
* The Assign Analysis Configuration Template step expects the input samples to be unpooled libraries.

## Known Issues

* On the Make Bulk Pool step, the log displays a warning when the Calculate Volume automation is triggered and at least one pool consists of multiple inputs. This issue is caused by the output custom field being reset multiple times at the end of the automation. This issue does not affect the Calculate Volume automation functionality.
* [Sample sheet and planned run generation will fail](/clarity-lims/known-issues/integration/set9561-sample-sheet-generation-fail-samples-with-qc.md) if any of the samples in the pools has been assigned QC flag in prior steps before entering the Load to Library Tube Strip step.
* For BCL Convert only analysis, the high level analysis summary file is not available. User will need to manually complete the AUTOMATED - Analysis Run step upon analysis completed.

## Revision History

| **Version** | **Changes**                                                                                                                         |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| 3           | <ul><li>Updated Known Issues section.</li></ul>                                                                                     |
| 2           | <ul><li>Updated Compatibility section to reference Compatibility matrix table.</li><li>Updated Known Limitations section.</li></ul> |
| 1           | <ul><li>Initial release.</li></ul>                                                                                                  |


---

# 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.connected.illumina.com/clarity-lims/instruments-and-integrations/novaseq-x-series/novaseqx/novaseqx-v1.2.0/novaseqx-v1.2.0-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.