> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/basespace/releases/previous-releases/2019/5.30.0.md). # 5.30.0 ### January 24, 2019 - 5.30 - NovaSeq SP Charts * Features * Updated the Charts tab to support NovaSeq SP runs. * Improved display of Biosample details and File Upload pages. * Added the project name to HTML title for the Project page. * Bugs Fixed * Biosamples created in multi-node FASTQ Generation were missing from the Run Samples tab in Classic mode. The biosamples are now listed in both New and Classic modes. * Improved detail for some file upload error messages. * Some successful file uploads briefly displayed an error message in Firefox browsers. * Cluster count values were displayed incorrectly in the Run Master List popup. The correct values are now displayed. * Security improvements in the developer portal. ### Release 5.30.1 - January 30, 2019 * Bugs Fixed * Fixed a slow loading issue on Analysis results pages. * Fixed an issue where an incorrect ID was returned for analyses launched via v2 API and CLI. * Fixed an issue where the View Files link for logs for some analyses did not appear on the Analysis summary tab. --- # 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.connected.illumina.com/basespace/releases/previous-releases/2019/5.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.