> 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/basespace/releases/previous-releases/2018/5.12.0.md).

# 5.12.0

### January 25, 2018 - 5.12 - Improvement to Biosample Workflow, Analysis Fixes

* Features:
  * Changed biosample workflow validation to allow duplicate biosamples for analysis.
  * Added dataset file dependency for analysis workflow auto-app launch.
  * Moved analysis details tabs from side to the top of the page.
  * Improved performance and stability for native apps (staged roll out completed: Jan 31, 2018).
* Bugs Fixed:
  * Fixed issue where files from aborted FASTQ Generation analyses could be used as inputs to downstream analyses.
  * Fixed display issue with Stats tab in Developer Portal.
  * Fixed issue with prep tab library creation unexpectedly showing "User container ID is required" error.
  * Fixed missing pool link on the run settings page for planned runs.


---

# 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.connected.illumina.com/basespace/releases/previous-releases/2018/5.12.0.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.