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

# 5.41.0

### December 17, 2019 - 5.41 - 'User' Column in Run List

### Features

* Added a User column to the runs master list to indicate which user uploaded the run.
* Enabled filtering in the projects Other Datasets tab.

### Bug Fixes

* Fixed an issue that could cause the biosample selection for app input to display an incomplete list of available biosamples.
* Fixed an issue that could prevent the trash from being emptied properly.
* Fixed an issue where the BaseSpace Downloader could not download files on OSX Catalina.

### Release 5.41.1 - January 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.41.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.