> 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/2017/4.27.0.md).

# 4.27.0

### June 21, 2017 - 4.27 - Bug Fixes for Display Issues and Deleting Through API

* Bugs Fixed:
  * Fixed issue with deleting completed analyses through the API
  * Fixed issue where the workgroup settings overview page was not displaying some information
  * Fixed text alignment in project delete confirmation modal

### Release 4.27.1 - July 18, 2017 - Started staged roll out

**FASTQ Generation**

* Updated bcl2fastq to 2.20
* New Features:
  * Added support for future NovaSeq flow cell releases
* Bug Fixes:
  * Fixed an issue that could cause FASTQ Generation to hang indefinitely with a small number of runs
  * Improved the robustness of FASTQ Generation when processing NovaSeq data that contains corrupted CBCL files


---

# 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/2017/4.27.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.
