> 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/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/known-issues-v6.3.x.md). # Known Issues for Clarity LIMS v6.3 The page lists the general known issues for Clarity LIMS v6.3.x . For each patch version, there may be additional known issues specific to it. Refer to the individual release notes for these. * In Add Label screen, the label will start at the well position at which user drops in when transferring the equivalent number of labels to samples in the output container at the first instance. * If the client and server are in different time zones, there can be additional or missing search results when using Date Received of a sample as one of the search criteria in Advanced Search. * Multiple accounts that share an email address only receive a reset password email for one of the accounts when a reset password request is made using Email information. * The step milestone screen becomes unresponsive when the request header/URL size is larger than the default capacity limit configured in either Apache HTTPD or Tomcat application server. * If there are changes made to the existing LDAP integration settings, restarting of Tomcat service will be required to provide the user access. * Clarity page will need to be refreshed after applying browser zoom in/out for proper display. This is mainly due to a limitation on ExtJS in which, the width that components take are only set when the page is refreshed. * Export and import of Project automations are not currently supported by Config Slicer tool. * Incorrect description of the sample's next step in Samples table in Next Step milestone - If Complete and Repeat routing action is added to the sample before the execution of the Step Automation (where the automation is having automatic upon step exit trigger), the sample is considered Completed and Repeated. The message "Repeated step and advanced" appears in the Next Step of the Samples table even though the step had failed at the EPP upon the step exit. * When searching for existing containers under Container Options in Ice Bucket milestone, the search result only retrieves the first 20 containers that match the search field and excludes those without available well slots. Relevant results that are beyond the first 20 containers are not returned. * Placement issue - when user does not place the samples starting from the first available well and the samples to-be-placed is more than the remaining available wells, the excess samples overflow to the remaining wells before the user selected well if those wells are available. * Column sorting issue for sample table in queue and ice bucket milestones - columns that are project global fields of toggle switch field type does not sort properly when values in the columns consist of only false and empty values. * In Projects and Samples, when creating new projects with closed status, the status of the newly created project on UI (with "Closed projects" filter selected) is updated after a short delay (less than a minute). This issue does not affect functionality. * Remote HTTP and HTTPS download of files and folders do not work on Clarity LIMS v6.3.2 and onwards. Refer to [Remote HTTP Filestore Setup - Troubleshooting](https://help.claritylims.illumina.com/api-and-database/api-docs/tips-and-tricks/remote-http-filestore-setup) for steps to work around the issues. Issue is fixed in Clarity LIMS v6.3.5 and onwards. * After artifacts are removed from QC protocol step queue, there is an additional QUEUED workflow-stage in the OpenAPI `/artifacts/id` response. * Automations configured with "ERROR" (uppercase) keyword in the script cause an error in the Clarity logs on Clarity LIMS v6.3.1 and onwards. Avoid using full uppercase "ERROR" keyword to work around the issue. * When a sample sheet submission fails in LabLink, the temporary project created during the submission remains visible in the project index and is searchable via Advanced Search. This issue is fixed in Clarity LIMS v6.3.5 and later, and LabLink v2.5.5 and later. * The Researcher role is needed to manage and work with samples in Clarity LIMS, including running automations, and for proper functioning of the integrations. **A custom role with the same set of permissions as Researcher would not suffice and cannot replace the Researcher role.** * For an on-premise in-place upgrade from Clarity LIMS v6.2 to v6.3, the Sequencer API RPM must be reinstalled if the `BaseSpaceLIMS-sequencer-api` RPM is present on the server. The [on-premise-to-on-premise-in-place-upgrade-procedures.md](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/on-premise-deployments/on-premise-to-on-premise-in-place-upgrade-procedures.md) article has been updated to include this step. * Search indexing may fail or stall when a sample contains a `reagentLabel` field value that exceeds the Elasticsearch keyword field size limit of 32676 bytes. This typically occurs when a large number of reagent labels are associated with a single sample. Refer to [search-indexing-troubleshooting.md](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/clarity-lims-v6.3-reference-guide/search/search-indexing-troubleshooting.md) for the workaround. * Config Slicer may produce an incomplete XML manifest export if a reagent kit name contains double spaces or line break characters, with no error logged to indicate the cause. Ensure reagent kit names do not contain double spaces or line break characters before running the export. * EPP automation error messages may fail to be reported back to Clarity LIMS when the API user password contains certain special characters, causing the Automation Worker to display a generic error instead of the actual script outcome. This issue is fixed in Clarity LIMS v6.3.6 and later. * The Project Summary statistics panel on the Projects & Samples page recalculates aggregate statistics on page load and periodically in the background, which can cause high CPU usage and database slowdowns on systems with many projects or derived samples. On Clarity LIMS v6.3.6 and later, this can be mitigated by setting `clarity.product.projectSummary.statsEnabled` to `false` in System Settings to hide the panel. * In LabLink v2.5.5.13 for Clarity LIMS v6.3.5 and LabLink v2.5.6.0 for Clarity LIMS v6.3.6, Project text-dropdown custom fields with custom entries disabled do not open on the Create Project page, preventing users from selecting an option other than the default. Enable custom entries as a workaround. This issue is fixed in LabLink v2.5.5.19 and v2.5.6.2, respectively. Contact Illumina Technical Support to obtain the applicable LabLink patch. --- # 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/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/known-issues-v6.3.x.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.