> 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.30.0.md). # 7.30.0 - Prep Tab Deprecation #### January 21, 2025 #### Features * Prep functionality is officially deprecated. All run planning and sequencer integration is available through the Run Planning tool. * Added the ability to export a Sample Sheet from the Run Planning Review page when the secondary analysis location is set to BaseSpace. * Improved performance when moving large projects to the trash. * Increased the size of the file preview modal. #### Bugs Fixed * Fixed an issue that could cause biosample workflows to time out during post-processing. * Fixed an issue that caused analysis post-processing to fail when a dataset name was too long. * Fixed an issue that prevented errors from displaying in Run Planning when using the Import Samples feature. * Improved the error message when importing sample data in Run Planning from a sample sheet with a different application version that what is currently selected. * Clarified a warning message when downloading FASTQ or SAV files from a run whose BCL files were deleted. * Clarified instructions in the Run Planning custom index adapter kit .tsv template. --- # 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.30.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.