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

# 5.40.0

### November 19, 2019 - 5.40 - Run Name Editing

### Important: Account Data Deletion

* We are turning on data deletion for inactive free accounts that have not logged in for 180 days or more.
* The system will send email notifications to inactive accounts warning them, and users have 30 days to reactivate their accounts by logging in.

### Features

* Enabled editing run names from either the run details page or the run master list (File | Edit | Run Info).
* Renamed the`Pending Execution` status to `Queued for Analysis`, and clarified the status tooltip description on the analysis master page.
* Renamed the run summary `Avg %Q30` metric label to `% ≥Q30`.

### Bug Fixes

* Fixed an issue that allowed share recipients to update the status of a run.
* We now are calculating project storage size based on Datasets instead of Samples and Appresults, this should be more accurate but may result in changes for some users. Staged roll out, estimated completion is 1/1/2020.

### Release 5.40.1 - November 26, 2019

* Features
  * None.
* Bug Fixes
  * Fixed an issue that prevented the download of analysis results.

### Release 5.40.2 - December 4, 2019

* Features
  * Bug Fixes
* Bug Fixes
  * Performance and stability fixes.

### Release 5.40.3 - December 9, 2019

* Features
  * None.
* Bug Fixes
  * Performance and stability fixes.


---

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