> 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/2019/5.34.0.md).

# 5.34.0

### May 16, 2019 - 5.34 - Performance Improvements and Bug Fixes

* Features
  * Performance Improvements.
  * Added the Illumina FASTQ File Upload Requirements help page link to the error message that appears when a user uploads a FASTQ file with an invalid naming convention.
  * Updated the Prep tab Biological Samples import page to include information about using library import when adding prepared libraries or samples with assigned indexes.
* Bugs Fixed
  * Fixed an issue that could prevent app launch when using biosamples from an Illumina Public Data shared project.
  * Added error messaging that displays when a file download attempt is made on an unsupported system.
  * Fixed an issue that could cause automatically launched workflows to immediately abort.
  * Fixed a formatting issue for long run names in the run master list run tooltip.
  * Fixed a formatting issue on analysis status tooltips.


---

# 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/2019/5.34.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.