> 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/novaseq-x-series/novaseqx/novaseqx-v1.1.0/novaseqx-v1.1.0-release-notes.md).

# Release Notes

Last Updated: November 2024

Release Date: September 2023

Document Version: 2

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

## **Compatibility**

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

## **New Features**

* Updated Java and third-party dependency libraries.
* Updated Groovy to v3.0.7.

## **Defects Fixed**

* Restricted the scope for the JWT token used in the integration.
* Fixed issue where the SIS core service was not properly registered in systemctl.

## **Known Limitations**

* This integration does not track the analysis step. You must log in to BSSH to view the cloud analysis status and results. For local analysis, the secondary analysis results are located in the external storage configured in Illumina Run Manager.
* The Local run mode does not support custom library prep and index adapter kits.
* The Analysis Configuration Template (ACT) names must be unique.
* 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.

## Revision History

| **Version** | **Changes**                                                                                                                         |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| 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 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/novaseq-x-series/novaseqx/novaseqx-v1.1.0/novaseqx-v1.1.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.
