> 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/2017/5.10.0.md).

# 5.10.0

### December 18, 2017 - 5.10 - Automatic Workgroup Switching and Additional API Security

* Features
  * Added prompt to switch to the correct workgroup context for the run when opening a run owned by a different workgroup.
  * Added more security to the bulk biosample import API when scheduling analysis workflows.
  * Updated look of app input form.
* Bugs Fixed
  * Fixed issue with the v1 appsession API showing v2 properties and vice versa.
  * Fixed issue with run requeues reaching the maximum number of retries after running multi-node Generate FASTQ.
  * Fixed issue with the run name being shown twice on the Run Summary page.
  * Fixed issue with the Generate FASTQ appsession being set to 'QC Failed' when one the FASTQ datasets it produced was manually set to 'QC Failed'.
  * Fixed issue with Charts on the Runs page sometimes not being shown after .bcl files for a run were deleted.
  * Fixed issue with the dashboard page not refreshing after accepting a shared or transferred run.


---

# 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/2017/5.10.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.