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

# 5.35.0

### June 11, 2019 - 5.35 - Increased File Upload Size Limit

* Features
  * The file uploader now supports up to 250 GB in a single session. However, for large files, the BaseSpace command-line interface (CLI) offers significantly faster upload times.
  * Performance Improvements.
* Bugs Fixed
  * Fixed an issue with empty biosamples not appearing in search results. Biosamples that have no data (no FASTQ data sets or all data sets are QC-failed) now appear in global search results.
  * Fixed an issue where links to deleted runs were not automatically removed from the Runs tab list.
  * Fixed an issue where the Yield calculation on the Run Summary tab was displaying the wrong unit of measure.
  * Fixed an issue where the analysis Inputs tab did not automatically refresh after an analysis was completed.
  * Fixed the default filters on the biosample chooser. When an app is launched from a project page, the available biosamples list is automatically filtered to show only biosamples from that project.


---

# 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.35.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.