> 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/2022/7.1.0.md).

# 7.1.0 - FastQ Related Fixes and Performance Improvements

### May 18, 2022

### Features

* Improved performance of biosample creation following the completion of run upload.
* Improved performance of QC failing existing FASTQ datasets when re-running BCL Convert.
* Added support for updating the default project on biosamples generated by the BCL Convert for ICA app.
* Added support for renaming biosamples generated by the BCL Convert for ICA app.

### Bugs Fixed

* Fixed an issue that could cause BCL Convert to fail when retrieving the number of flow cell lanes.
* Fixed an issue that caused deleted FASTQ datasets to remain visible on the Run Biosamples page.
* Fixed an issue that could cause apps to fail when selecting large numbers of datasets as input.

### Release 7.1.1 - May 19, 2022

* Features
  * None.
* Bugs Fixed
  * Performance and stability fixes.

### Release 7.1.2 - June 22, 2022

* Features
  * None.
* Bugs Fixed
  * Security 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.connected.illumina.com/basespace/releases/previous-releases/2022/7.1.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.
