> 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/2024/7.26.0.md). # 7.26.0 - Prep Tab Obsolescence Notification #### September 17, 2024 #### Features * Prep functionality is being deprecated. Starting in January 2025, the Prep tab will no longer be available. Most users have already upgraded to use Run Planning. It is recommended any legacy NextSeq and MiniSeq users update to the latest software releases for their platform. * Archive is now available for all runs and datasets, including data from NovaSeqX and NovaSeqXPlus instruments. * ICA analysis logs have been moved to a dataset called "ICA Logs", to make them easier to find in the Analysis Files UI. * Added the ability to requeue a Run from the Run list. #### Bugs Fixed * Fixed an issue that prevented the index cycles from displaying on the Run Summary tab before the upload completed. * Fixed an issue that could cause a run with a bad sample sheet to get stuck in 'Pending Analysis' rather than moving to 'Needs Attention'. * Fixed an issue that allowed a run to be transferred before the upload completes. * Fixed an issue that could prevent the Run Indexing QC tab from displaying properly. * Fixed an issue that could send duplicate "run created" emails when starting a sequencing run. --- # 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/2024/7.26.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.