> 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.35.0.md). # 7.35.0 - Display Cost for Completed ICA Analyses #### June 17, 2025 #### Features * Final compute cost is now displayed for analyses that execute in ICA. * Added the ability to delete an analysis when data is partially owned by another user (i.e., following a project transfer). Only data owned by the user will be deleted, and other users with analysis data will retain access to the analysis details. * Updated the file preview modal to include a link to the analysis files tab. The link appears when viewing a file without the analysis context, such as in search results. * Added a note on the Microarray Analysis Setup sample selection page to indicate when a sample sheet with additional information is recommended for the selected analysis. * Added an info icon with an explanatory tooltip when a run's data status is 'Zipped' or 'Zipping'. #### Bugs Fixed * Fixed an issue that could cause an analysis details page to get stuck while loading. * Fixed an issue that could result in an error when attempting to empty the trash or restore items. * Fixed an issue that could cause 'analysis completed' emails to be erroneously sent immediately after launching certain apps. --- # 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.35.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.