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

# 5.39.0

### October 17, 2019 - 5.39 - Improved performance of FASTQ file importing

* Features
  * Improved performance of FASTQ file importing via web upload.
* Bug Fixes
  * Fixed an issue that allowed projects with outstanding transfer invitations to be moved to the trash.
  * Fixed an issue where Run Name and Flow Cell ID did not appear in FASTQ Dataset tab tooltip.
  * Fixed an issue where the dashboard link to the developer portal did not display for Enterprise users.
  * Fixed an issue where bookmarked apps might not appear in the bookmark widget.
  * Fixed an issue that caused long workgroup lists to load slowly.

### Release 5.39.1 - October 28, 2019

* Features
  * None.
* Bug Fixes
  * Fixed an issue that could cause the workgroup list to hang indefinitely.


---

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