> 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/nextseq550-v2.1.0-release-notes.md).

# NextSeq 500/550 v2.1.0

These Release Notes detail the key changes to software components for the Clarity LIMS NextSeq 500/550 Integration Package since version 2.0 of that package.

This is an optional software update for customers interested in the new features available with this new release.

If you are upgrading from a version prior to version 2.0 please review the release notes for version 2.0 for a list of features and bug fixes introduced in that version.

## Compatibility

* Clarity LIMS v4.2 through v5.4
* NGS Extensions Package v5.19 or later
* Preconfigured Workflow Package (PCWP) v2.0.1 or later
* Illumina Preset Protocols (IPP) v2.0.0 or later
* NextSeq Control Software (NCS) v4.0 (Standalone mode, only)

## New Features

This release of the Clarity LIMS integration package:

* Supports the security improvement made to the management of passwords in Clarity LIMS v5.4.
* Provides an updated run report with the Clarity LIMS footer.
* Delivers a NextSeq preconfigured workflow as part of PCWP 2.0.1 or IPP 2.0.0, which can be installed via support request.

## Defect Repairs

The SequencerApi proxy configuration script now correctly updates the clarity.conf file.

## Known Issues

None


---

# 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/nextseq550-v2.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.