24R3 Maintenance Releases


A “maintenance release” is a release that contains fixes for issues that are affecting customers in production environments. We communicate 24 hours prior to the release that we will be applying a maintenance release and that there will be a short service disruption. This list only covers fixes to General Release versions.

The list of fixed issues is not finalized until just before the release occurs. When we identify issues to fix in a maintenance release, we attempt to get them into the earliest release possible. Sometimes, we target a specific release but are not able to deliver a fix early enough for full testing. In situations like this, we postpone the fix for a later release and strike out the description in this list.

We number maintenance releases by appending the number of the maintenance release to the General Release number. Vault CDMS uses odd-numbered releases, while Vault uses even-numbered releases. The most recent General Release was 24R3, so our maintenance releases for this version are 24R3.0.3, 24R3.0.5, and so on.

December 2024


December 6, 2024

Release Number: 24R3.0.3 | Build Number: TBD CDMS

Category Issue Description Issue No.
Deployment During high traffic periods, due to cookie name creation, users may encounter a "Could not find SessionID" error when attempting to copy from Production vaults to PPT vaults. VDC-175810, VDC-175843
Rule Execution For studies using Rule Expression Engine V1, some rules referencing blank values display an unexpected error upon Form submission. VDC-175238
Study Design Archiving a User Defined Rule makes the object counts in Studio > Study Objects display as "0". VDC-175704

Release Number: 24R3.0.3 | Build Number: TBD CDB

Category Issue Description Issue No.
CDB - Checks Marking a form as Intentionally Left Blank or resetting a Form deletes the system query, instead of closing it. VDC-173894
CDB - CQL In incremental import studies, Call Sys_Forms may return a "Failure in Executing" error. VDC-175095
CDB - Import Incremental import doesn't account for precision correctly with a maximum length on the Item. VDC-172995