> 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.37.0.md). # 7.37.0 - Analysis Details "Orchestrated Analyses" Section #### August 19, 2025 #### Features * Added an "ICA Orchestrated Analyses" section to the Analysis Details page for autolaunched analyses. The section displays the status and details of each individual analysis launched. * Added a link to Usage Explorer in the header waffle menu. * Switching to the Usage Explorer now retains the current workgroup context. Only admins can see workgroup or domain-level usage. #### Bugs Fixed * Fixed an issue in the Analysis Files tab that occurred when multiple datasets with the same name existed, causing only one to be displayed. * Fixed an issue that could prevent pricing information from displaying on the App details page. * Fixed an issue that could prevent an app from transitioning to 'Complete' when no output datasets were produced. * Fixed an issue on the Analysis Details page that could display a link to a Project the user does not have access to, resulting in a 403 Forbidden page when clicked. #### Known Issues * The copy and merge features are currently unavailable for samples generated by BCL Convert. --- # 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.37.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.