> 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.31.0.md). # 5.31.0 ### February 6, 2019 - 5.31 - Improvements to App Launch * Features * Improved launch of apps with up to 384 samples to avoid a time-out. * Workgroup administrators can now manage workgroups. * Bugs Fixed * When uploading a VCF with a file name that exceeds the character limit, the error message now indicates that the filename is too long. * Uploading files to the website over a slow internet connection no longer causes a time-out. ### Release 5.31.1 - February 8, 2019 * Features * Performance improvements. * Bugs Fixed * None. ### Release 5.31.2 - February 11, 2019 * Features * Expected yield is now only calculated for biosamples with 32 datasets or less. For biosamples with more than 32 datasets, expected yield will equal the actual yield. * Bugs Fixed * Fixed an issue that could cause discarded fastq datasets to be submitted when launching apps with biosample inputs. Staged roll out completed Feb 12. ### Release 5.31.4 - February 26, 2019 * Features * Performance improvements. * Bugs Fixed * Fixed an issue that caused some apps get stuck in the "Payment Pending" state. ### Release 5.31.5 - March 6, 2019 * Features * None. * Bugs Fixed * Fixed an issue where users were taken to an Unexpected Issue page when launching certain apps. * Fixed an issue in New mode that could cause apps to launch with incomplete FASTQ datasets. --- # 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.31.0.md?ask=&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.