> 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/2022/6.19.0.md). # 6.19.0 - ICA Integration Enhancements ### March 15, 2022 ### Features * Projects, datasets, and analyses with files stored in ICA can now be moved to the trash and deleted. ### Bugs Fixed * Fixed an issue with the Instrument Run Setup tool, where the Lane column was incorrectly validated when using “Not Specified” for library prep kit. * Fixed an issue that could incorrectly set the size of an Analysis to 0. * Fixed an issue on the Run Sample Sheet tab where Date field values were incorrectly formatted. ### Known Issues * FASTQ Generation and other apps very infrequently abort while uploading results. * For customers using Instrument Run Set up to create a v2 sample sheet for a NovaSeq SP 500 cycle run, the sample sheet produced has the I5 index sequence in the incorrect orientation. This assigns all sample reads to undetermined. To correct the issue, we recommend removing the "IndexOrientation Forward" flag from the \[Header] section of the sample sheet. ### Release 6.19.1 - March 31, 2022 * Bugs Fixed * Fixed an issue in the application editing page used by administrators. --- # 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/2022/6.19.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.