> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/design-studio-array/reference/release-notes/designstudio-array-v2.2.0-release-notes/designstudio-array-v2.2.1-release-notes.md).

# DesignStudio Array v2.2.1 Release Notes

#### Release date

August 2024

#### NEW FEATURES

* None

#### FIXED ISSUES

* Fixed issue impacting the addition of Commercial+ (semi-custom) EX BeadChips. Semi-custom EX BeadChips can now be created.

#### KNOWN ISSUES

* Non-specific failures occur when:
  * Loci names include two dashes ("--") in the input file.
  * A M or MT chromosome designation is used for equine as species.
  * Submitting sequence files with certain formatting errors. The workflow terminates without allowing access to the error file.
* When using an existing design file, a dropdown exists but the stand type cannot be changed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.connected.illumina.com/design-studio-array/reference/release-notes/designstudio-array-v2.2.0-release-notes/designstudio-array-v2.2.1-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.