> 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/2020/6.2.0.md). # 6.2.0 ### October 13, 2020 - 6.2 - Instrument Run Setup Enhancements ### Features * Added the selected analysis name and version to the Analysis Setup section of Instrument Run Setup * Added description of selected library prep and index adapter kits below each field in Instrument Run Setup. * Increased the character limit for project names to 255. ### Bugs Fixed * Fixed an issue on the Run list that could cause a blank popup to appear when filtering a column. * Fixed an issue that could cause users to revert to the personal context while in a workgroup. * Fixed an issue that caused the delete menu option to be disabled for shared runs. * Fixed an issue that caused a failure to delete error message to appear after a planned run was successfully deleted. * Fixed an issue in the Planned Run list that would display Index2 length values for single index runs. * Fixed an issue that caused dropdown menus in Instrument Run Setup to display truncated names. * Improved performance of the /v2/preprequests API endpoint. * Fixed an issue with app input forms that could cause choosers to remain available when nested in a radio component. --- # 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/2020/6.2.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.