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

# 5.14.0

### February 20, 2018 - 5.14 - Bug Fixes

* Features:
  * Added capability to product switcher dropdown menu to dynamically update for available Illumina products
* Bugs Fixed:
  * Fixed issue with missing Metrics link on analyses pages for both imported files and FASTQ Generation runs.
  * Fixed rare issue with the Regenerate FASTQ where action could occur more than once for a run when button was clicked more than once.
  * Fixed issue where editing a project description did not lead to automatic refresh of the project page.
  * Fixed issue where the infinite scrolling on the apps list did not work properly when loading the page with large browser windows.
  * Fixed an issue where the summary metrics tooltip in the Runs list showed metrics for Index Read 1 instead of Data Read 2 for "R2"
  * Fixed issue with inconsistent dates for the billing cycle on the dashboard widget and the user settings storage page.


---

# 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/basespace/releases/previous-releases/2018/5.14.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.