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

# DesignStudio Array v3.1.0 Release Notes

#### Release date

March 2026

#### Key Highlights

* New **Array Finder** tool to match up to **50k variants (rsID/cgID) or genomic loci** against Illumina commercial base content.
* Supports **target entry through the UI or file upload** using a template.
* Allows selection of the **species genome build** (for example, *Homo sapiens* build 37 or 38) before running the search.
* Displays a **summary of overlapping targets across commercial arrays** with downloadable summary and detailed results files.
* Outputs an **excludedContent** file listing targets excluded from the search.

#### Resolved Issues

* Improved bin assignment for Infinium I indels by categorizing insertion and deletion variants. This helps organize genetic data for accurate identification and interpretation of variants.

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