> 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/2021/6.9.0.md).

# 6.9.0

### May 25, 2021 - 6.9 - Subscription Details

### Features

* Added the % Reads Identified chart to the Indexing QC page.
* The Account Overview settings page now displays subscription expiration date, subscription status, and iCredit balance.
* Changed instrument-specific option label in New Run menu to "Instrument Run Setup".
* Improved Instrument Run Setup user experience when importing a sample sheet with a defined Index Adapter Kit.

### Bugs Fixed

* Fixed an issue with the default order of entries on the Demo Data page. Entries are now sorted chronologically with newer entries listed first.
* Improved messaging for sample report generation failure.
* Fixed an issue that caused the Upload Biosample Manifest modal to close when users click outside the modal.
* Fixed an issue that disabled dataset links on the Run Biosamples page.
* Fixed an issue that showed an empty Run Biosamples page for projects owned by another user.
* Fixed an issue on the Run Metrics page where the table headers did not display after saving the metrics as a PDF.


---

# 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/2021/6.9.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.