> 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.41.0.md). # 7.41.0 - Run Planning Improvements #### December 16, 2025 #### Features * Enhanced Run Planning to display warnings, e.g. for deprecated apps * Updated "Local" Analysis Location label in Run Planning to "On Instrument (Local)" * Enhanced Run Planning to retain BCL Convert per-sample settings imported from sample sheet * Improved performance of deletes with large number of items * Better cleanup of background processes preventing project transfer #### Bugs Fixed * Fix login from certain instruments where user needs to accept agreements * Prevent users from seeing and deleting hidden analyses * Fixed issue where QC recalculation could fail if appsession wasn’t complete, causing downstream workflows to misfire. QC update now occurs only after appsession completion to ensure correct status transitions. * Improved billing for some older apps * Security and performance fixes #### 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.41.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.