> 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.25.0.md). # 7.25.0 - Project Column in the Analysis Files Tab #### August 20, 2024 #### Features * Updated the Analysis Files tab to include a project column with the associated output project. * Runs will now transition to the "Timed Out" status if they have not completed 14 days after upload starts, or 8 days after secondary analysis starts. * Reordered the items in the Status > Requeue menu. * Deprecated NeoPrep functionality. * Minor UI updates and fixes. #### Bugs Fixed * Fixed an issue that could prevent the sample sheet from loading on the Requeue Sample Sheet page when a custom sample sheet name was used. * Fixed an issue that could prevent requeueing runs that were uploaded without an initial sample sheet. * Fixed an issue where BCL Convert 2.5.0 was not updating the run status upon completion. * Fixed an issue that prevented unzipping a zipped run when the run folder contained a Logs.zip file. #### Release 7.25.1 - August 29, 2024 * Features * None. * Bugs Fixed * Fixed an issue that could cause the Analysis Reports tab to display a blank space instead of a report. * Stability and performance improvements. --- # 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.25.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.