> 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.29.0.md). # 7.29.0 - Improved Analysis Error Reporting #### December 17, 2024 #### Features * Added improved error reporting for supported analyses, such as those auto-launched from NovaSeq X and MiSeq i100 instruments. A link in the logs section of the Analysis Summary tab opens a modal displaying a list of failed steps and relevant log file contents. #### Bugs Fixed * Fixed an issue that could cause analyses to complete before all datasets are created. * Improved the messaging for certain errors that could occur when requeueing an analysis in Run Planning. * Fixed an issue that could cause an 'unknown settings found' error after selecting a BCL Convert version in Run Planning. * Fixed an issue that caused the requeue menu option to be enabled for monitoring-only runs. * Fixed an issue that prevented node statuses from updating automatically on the Analysis Details page. * Fixed inconsistent timestamp formats on the Analysis Details page. #### Known Issues * When running MacOS Sequoia, the BaseSpace Downloader throws an error on download. Leaving the Downloader open and retrying will allow it to start successfully. --- # 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.29.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.