> 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.24.0.md).

# 5.24.0

### July 17, 2018 - 5.24 - Display and Filtering Bug Fixes

* Bugs Fixed
  * Fixed an issue with the applications API returning an incorrect total count when getting a list of applications.
  * Fixed an issue with the Classic/New banner information icon in the Frankfurt/EU instance incorrectly linking to the US help files.
  * Fixed an issue with the My Illumina selection redirecting to the last-visited Illumina page instead of the account settings page.
  * Fixed a display issue with data point tooltips in Run Charts not displaying on screen.
  * Fixed a display issue with the FASTQ file upload library prep kit dropdown. The list of the display is widened to fit long prep kit names.
  * Fixed a filtering issue in New mode. The .bed filter in the app input file chooser incorrectly returned .txt files in addition to .bed files.


---

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