> 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/2025/7.36.0.md). # 7.36.0 - Analysis Size Display #### July 22, 2025 #### Features * Updated the analysis size display to only reflect datasets the user has permissions to view. #### Bugs Fixed * Fixed an issue that could cause an autolaunched analysis to be marked as complete before all downstream analyses finished. * Fixed an issue that could cause samples produced by the FASTQ Generation app to appear twice in the Analysis Reports tab, and to download duplicate FASTQ files when downloaded. * Fixed an error that could occur when attempting to delete a project using the CLI or API. * Fixed an issue that caused timed out runs to get stuck in 'Pending Analysis' after launching an analysis. * Fixed an issue on the Analysis Reports tab that displayed a summary link when no summary report existed. * Fixed an issue that caused PDF files to immediately download when opening them in a preview window. #### Known Issues * The copy and merge features are currently unavailable for samples generated by BCL Convert. #### Release 7.36.1 - August 11, 2025 * Features * None. * Bugs Fixed * Stability and performance improvements. --- # 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/2025/7.36.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.