> 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/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/release-notes-clarity-lims-v6.3.1.md).
# Release Notes Clarity LIMS v6.3.1
Published: November 04, 2024
Last Update: September 2025
Latest Release: v6.3.1
This Release Notes describe the key changes made to software components for Clarity LIMS v6.3.1. The Clarity LIMS v6.3.1 patch release supersedes v6.3.0. It is intended for customers on or migrating to Clarity LIMS v6.3.1.
{% hint style="info" %}
Note: All customers on Clarity LIMS v6.3.0 are strongly recommended to upgrade their instance(s) to Clarity LIMS v6.3.1.
{% endhint %}
This release resolves customer-reported issues related to the following functions:
* OpenAPI endpoint (POST /artifacts/batch/update) failure
* Change in Basic search functionality
* SSH access cannot be requested for username with period.
### New Features
There are no new features added with this release.
### Bug Fixes
* Fix a bug where openAPI endpoint (POST /artifacts/batch/update) returns error when user attempts to submit a batch update request that includes at least 50 artifacts of one type and 1 artifact of another type , example, 50 artifacts (Derived Sample) and 1 artifact (Measurement).
* Fix a bug that prevents File placeholder from displaying the full text value in Step Setup screen.
* Fix a bug where SSH request made through System Settings, do not allow period (.) as part of the provided username.
* Basic search is now case-insensitive for limids and workflow.
* Fix a bug where Automation Worker becomes unresponsive after cancelling an ongoing automation job in a step multiple times.
* Fix a bug where auditeventlog has incomplete event message "Creating new file attached to" when attempting to upload a file attached to a measurement (ResultFile). The event message now displays "Creating new file attached to ResultFile".
* Fix a bug where config slicer tool takes longer time (\~8 times) to import a config slice into Clarity LIMS v6.2 and v6.3 when compared to earlier versions (v6.1 and below).
### Known Issues
Refer to [Known Issues for Clarity LIMS v6.3](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/known-issues-v6.3.x.md) for list of known issues for Clarity LIMS v6.3.
### Additional Notes
Refer to [Additional Notes for Clarity LIMS v6.3](/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/additional-notes-v6.3.x.md) for list of additional notes for Clarity LIMS v6.3.
The following are additional notes applicable to Clarity LIMS v6.3.1:
* Font used for some of the UI components has been changed from DINWeb to Inter v4.0.
* Dependancy version upgrade:
* upgraded to Apache Standard Taglibs v1.2.5
* upgraded to Lodash v4.17.21
* upgraded to apache-poi v5.3.0
* upgraded to jackson-core v2.17.2
* PostgreSQL 15.13 has been assessed to be at low risk of security vulnerabilities and has been shown to have no functional impact on Clarity LIMS v6.3.1.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.connected.illumina.com/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/readme/release-notes-clarity-lims-v6.3.1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.