> 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/2018/5.20.0.md).

# 5.20.0

### May 15, 2018 - 5.20 - New Run Chart Options and v2 APIs

* Features
  * Added new % PF option to Flow Cell chart for all sequencing instruments, and % occupancy to Flow Cell charts and Data by Lane plot for iSeq100 and MiniSeq.
  * Added v2 API endpoint to provide default workgroup storage location information for a user or workgroup.
  * Now automatically timing out existing runs sitting in an active status for 90 days or more.
* Bugs Fixed
  * Fixed an issue with auto-logout logging out users before the 30 minute mark.
  * Fixed an issue with login sessions expiring during large project file imports.
  * Fixed issue with project file upload sessions failing to auto-complete when the user is inactive for a few minutes.
  * Fixed issue with the run summary page initially scrolling down below the navigation tabs upon loading.
  * Fixed incorrect sum in TotalCount of the v2 applications API.


---

# 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/2018/5.20.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.