> 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/design-studio-array/reference/release-notes/designstudio-array-v3.0-release-notes.md).

# DesignStudio Array v3.0 Release Notes

Version DSA 3.0 delivers the Methylation Release, introducing major enhancements to probe design workflows, expanded Illumina Connected Analytics (ICA) integration, improved performance, and numerous.

#### Release date

January 2026

#### Methylation Enhancements

* Dedicated **Methylation Designer** updates, including improved handling of excluded content, normalization bins, error reporting, and output file structures.
* Support for additional commercial panels and improved error handling in test runs.
* New controls and validation checks for probe design integrity.

#### Illumina Connected Analytics (ICA) Integration

* Direct ICA pipeline launch from DSA.
* Subscription and access improvements (dynamic subscription creation, handling delays, public domain access).
* File management and ICA analysis consumers fully integrated.
* Expanded endpoint coverage for design status, events, coordinates, and target retrieval.

#### User Experience & Interface

* Updated tooltips, toggles, and styling.
* Improved species selection and population handling.
* Enhanced download templates and output file formats.
* New options for orderability checks and commercial probe management.

#### Known Issues

* Validation error does not occur when submitting an empty input file
* Invalid characters in design names do not trigger an error
* Email templates still include some irrelevant error and warning codes
* Intermittent UI error may occur in Chrome


---

# 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/design-studio-array/reference/release-notes/designstudio-array-v3.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.
