> 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.0.3-release-notes.md).

# NextSeq 500/550 v2.0.3

## Compatibility:

* BaseSpace Clarity LIMS v4.2 to v5.x
* NGS Extensions Package v5.17 or later
* Preconfigured Workflows Package (PCWP) v1.x

## Illumina NextSeq Software Compatibility:

* NextSeq Control Software (NCS) v4.0
* This integration only supports Standalone mode on NCS v4.0.

## Features to note for this release

This release includes the following:

* Support for NextSeq Control Software (NCS) v4.0. The NextSeq batch file (gls\_event\_ncs\_rta.bat) updated to pull the sequencing run output folder network path from the RunParameter.xml file, as NCS v4.0 no longer outputs the path as a string.

## Issues resolved in this release

The following issues were resolved in this release:

* Incomplete content in Runreport.pdf
* Incorrect FinishDate in EndRun event file


---

# 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.0.3-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.