A maintenance release contains fixes for issues affecting customer Vaults in production environments. Maintenance releases can occasionally include enhancements, for example, a time-sensitive regulatory requirement. This page covers maintenance releases deployed to General Release Vaults only. We communicate 24 hours prior to a maintenance release. There may be a short service disruption during deployment.
This list only covers fixes for issues that impact 25R3 General Release versions of Safety Vaults. The list of fixed issues is subject to change until 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 for Safety by appending the number of the Safety-specific maintenance release to the General Release number. The most recent Veeva Vault General Release is 25R3.0, so our maintenance releases for this version are 25R3.0.2, 25R3.0.3, and so on.
Veeva Vault frequently delivers Platform maintenance releases. Safety deploys these Platform maintenance releases at a later date, along with any required fixes to Safety. For details on Platform fixes in these maintenance releases, see 25R3 Maintenance Releases.
Last Updated: December 16, 2025
December 16, 2025
Release Number: 25R3.0.9 | Build Number: 212 | Platform: 10393
| Description | Issue No. |
|---|---|
| When generating MFDS E2B(R3) files, Vault detects an error for the C.5.4.KR.1 data element and moves Submissions into the Validation Error state, instead of the Ready state. | SAF-92893 |
| When generating E2B(R3) files, Vault does not convert the TermID Version to YYYYMMDD format when populating the G.k.2.3.r.2a data element, resulting in NACKs. This issue does not impact MFDS E2B(R3) files. | SAF-92983 |
|
If a Case Assessment is created without a Case Product or a user manually clears a Case Product on a Case Assessment, users may experience performance issues. |
SAF-93318 |
December 12, 2025
Release Number: 25R3.0.8 | Build Number: 204 | Platform: 10386
| Description | Issue No. |
|---|---|
| In some instances, during promotion of an Inbox Item with a high number of Products, an error occurs during duplicate detection, which prevents case processing. | SAF-91274 |
| In Vaults with the "Related Case Identifier source (On Edit)" application setting enabled, users may experience performance issues following changes to the Related Case on a Case Relationship record. | SAF-93138 |
December 10, 2025
Release Number: 25R3.0.7 | Build Number: 202 | Platform: 10372
| Description | Issue No. |
|---|---|
| During approval of a global follow-up Case with a related foreign follow-up Localized Case for the NMPA, users experience performance issues while Vault performs the one-time data sync from the global to the Localized Case. | SAF-93050 |
December 8, 2025
Release Number: 25R3.0.6 | Build Number: 199 | Platform: 10368
| Description | Issue No. |
|---|---|
| When processing a Case that includes some, but not all, constituents of a Combination Product, users experience significant performance issues when Vault maps and creates Case Product records for the remaining constituents. | SAF-92838 |
| When Vault performs the one-time data sync from a global follow-up Case to a foreign follow-up Localized Case for the NMPA, users experience significant performance issues when Vault syncs Case Assessment Results. | SAF-92862 |
December 4, 2025
Release Number: 25R3.0.4 | Build Number: 193 | Platform: 10359
| Description | Issue No. |
|---|---|
| In some cases when coding an External Product using the WHODrug Search browser, Safety does not populate the TermID Version field on the generated Substance records, triggering a validation error. | SAF-90116 |
| In some cases upon removing a Yes/No filter from a Workbench Dashboard, Workbench encounters an error and displays a blank dashboard. | SAF-90836 |
| In Vaults without the Enable Isolation of Blinded Product Information setting enabled, after populating the Combination Product field on an unblinded Study Product within a Case that already contains one or more of the Study Product constituents as Case Products, Vault creates duplicative Case Products for those constituents. | SAF-91437 |
| In some cases when accessing a Case with failed Validation Results, Vault displays a record count of 0 for Validation Results (Failures & Warnings) in the sidebar. | SAF-92139 |
| When generating a Transmission to the NMPA for a foreign follow-up Localized Case for China, if multiple Case Assessment Results have the same Relatedness value, an error occurs during the one-time sync from the global Case to the Localized Case, and Vault prevents additional Case processing. | SAF-92319 |
November 26, 2025
Release Number: 25R3.0.3 | Build Number: 180 | Platform: 10341
This release contains no customer-facing fixes.
November 23, 2025
Release Number: 25R3.0.2 | Build Number: 177 | Platform: 10334
This release includes only Platform fixes.