> 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/2018/5.29.0.md). # 5.29.0 ### December 11, 2018 - 5.29 - FASTQ Filename Validation and App Bookmarking * Features * Added bookmarks to the app landing page. Bookmarked apps are listed in the sidebar adjacent to the apps list. * Added filename validation to uploaded FASTQ files. To prevent potential downstream app failure, the web uploader does not allow filenames that contain special characters. * A confirmation email is now sent when an inactive user reactivates their account by logging in. * Improved UI * Tabbed pages no longer display a subheader if the subheader is a duplicate of the tab name. * Initial Lane & QC Status label on the runs page is listed as Initial. Initial status was originally displayed as --. * The creation and updated dates for all resources in BaseSpace Sequence Hub are now formatted according to ISO-8601. * Bugs Fixed * Fixed an issue that caused problem when attempting to switch workgroups when the window size is small. * Fixed an issue that prevented some users from downloading project files when in New mode. * Fixed some display issues in Safari. --- # 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/2018/5.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.