> 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/2026/7.43.0.md). # 7.43.0 - Copy And Merge All Samples #### February 17, 2026 #### Features * Restore the ability to copy and merge new samples created by the latest versions of BCL Convert. * Updated run details page to always show the latest %demux when the metric is available. * Native analyses are not marked complete until all post-processing (including converting samples to datasets) has been completed. * Add Oregon (USW2) as a publicly available BaseSpace region. * Run Planning only shows the custom adapter option when supported by the selected application. * Security and stability improvements. #### Bugs Fixed * Fixed an issue where a shared workflow's details (breakdown of orchestrated analysis, steps, and detailed logs) were not viewable by the recipient. * The Analysis->Files page now displays the output from multi-node analyses with large numbers of child analyses. * Improve information captured when using application tokens for BaseSpace API operations. * Application tokens can be used to accept share and transfer invites. * Changes to the number of rows in website tables are now captured in cookies and are remembered between visits. --- # 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/2026/7.43.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.