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. We typically 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.
This list on this page covers only fixes for issues that impact 26R1 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 26R1.0, so our maintenance releases for this version are 26R1.0.2, 26R1.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 26R1 Maintenance Releases.
Last Updated: May 25, 2026
May 27, 2026
Release Number: 26R1.0.13 | Build Number: TBD | Platform: TBD
| Description | Issue No. |
|---|---|
| On Localized Cases, Vault does not map Local MPIDs from Combination Product Registrations to Localized Case Products. | SAF-99881 |
| On the Inbox Item to Case Compare page, Vault does not allow users to merge an Inbox Item to an in-flight Case with more than 500 products. | SAF-100496 |
| On the Inbox Item to Case Compare page, Vault merges data for sections with more than 500 records when the user has selected Ignore All. | SAF-100831 |
| On the Inbox Item to Case Compare page, if a user clears all filters and then selects Ignore All, Vault ignores data from the first page of records but merges data from subsequent paginated records for the ignored section. | SAF-102793 |
| After coding external products with WHODrug Global Chinese codes, Vault does not populate the Preferred Name in the Trade Name field of Localized Case Products. | SAF-103631, SAF-103949, SAF-105441 |
| When generating NMPA E2B(R3) files, Vault does not populate the Dose (Number) from the Case Product Dosage in the G.k.4.r.1a data element if the corresponding Dose (Unit) is not supported and {DF} appears in the G.k.4.r.1b data element. | SAF-104229 |
| When generating NMPA E2B(R3) files, Vault does not populate the G.k.4.r.4 data element if the First Admin Date of the Case Product Dosage is earlier than the Local Initial Receipt Date. | SAF-105164 |
| For imported Cases on the Potential Matches page, Vault masks source and matched records for users in access groups that grant permissions for protected health information (PHI) and personally identifiable information (PII). | SAF-105546 |
May 21, 2026
Release Number: 26R1.0.12 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
Release Number: 26R1.0.11 | Build Number: 243 | Platform: 10506
| Description | Issue No. |
|---|---|
| This update optimizes code for unknown formulation product verification. This will be available for configuration in a future release. | SAF-105112 |
| When generating EMA E2B(R3) files with Turkey as the destination, Vault does not populate the G.k.9.i.2.r.2.EU.1 data element. | SAF-100186 |
| On follow-up Cases created through Automated Case Promotion with the Override merge method, Vault incorrectly orders the initial and follow-up narrative versions. | SAF-102855 |
| On Cases promoted from JSON-imported Inbox Items with a non-global Localization, an error occurs when loading Case Product Indications if multiple localized MedDRA terms exist for a global MedDRA term. | SAF-102960 |
| When regenerating a rules based narrative would result in a blank follow-up summary of changes, Vault does not update the follow-up summary. | SAF-103769 |
| An error occurs when creating foreign follow-up Localized Cases for Japan when duplicate Case Product Registration records and a high volume of Localized Case Assessments exist. | SAF-105160 |
| When generating EU MIR forms, to determine whether to select the 1.2g option "Unanticipated serious deterioration in state of health", Vault considers all Case Assessment Expectedness values instead of only those linked to the Case Product on the Transmission. | SAF-105808 |
May 20, 2026
Release Number: 26R1.0.10 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
May 14, 2026
Release Number: 26R1.0.9 | Build Number: 232 | Platform: 10474
| Description | Issue No. |
|---|---|
| When generating NMPA E2B(R3) files, Vault does populate a value in the G.k.CN.4 data element if no applicable Product Registrations exist, resulting in NACKs. | SAF-102590 |
| When generating EU MIR forms, Vault truncates unique device identification (UDI) values in section 2.1 and populates section 4.3.1a when the source fields on the Case are blank. | SAF-103023 |
| Selecting the Modified filter button on the Case Version Compare page does not filter the display to only newly added or modified records and fields. | SAF-103025 |
| In some instances, users experience AS2 Connection issues when Vault attempts to transfer files between Safety and an AS2 gateway. | SAF-103579 |
| When generating NMPA E2B(R3) files for Cases with Combination Products, Vault populates the G.k.CN section for device product constituents, resulting in NACKs. | SAF-103774 |
| When generating EU MIR forms, regardless of the Scientific Opinion Asked or Competent Authority Consulted values on the Device-type Case Product, Vault always selects No in section 2.4f. | SAF-103782 |
| When generating an NMPA E2B(R3) file for a Case promoted from an Inbox Item containing a Product coded using the Product Browser, Vault maps the Trade Name value from the Product Registration. | SAF-104053 |
May 13, 2026
Release Number: 26R1.0.8 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
May 8, 2026 (Postponed) May 10, 2026
Release Number: 26R1.0.7 | Build Number: 224 | Platform: 10426
| Description | Issue No. |
|---|---|
| In Vaults configured for advanced product match coding verification, when transferring serious adverse events (SAEs) through the Safety-EDC Connection, an error occurs and prevents Inbox Item generation in the Safety Vault. | SAF-105549 |
May 7, 2026
Release Number: 26R1.0.6 | Build Number: 222 223 | Platform: 10426
| Description | Issue No. |
|---|---|
| This update optimizes code for DSUR generation. This will be available for configuration in a future release. | SAF-101963 |
| When generating the August 2024 version of the FDA MedWatch 3500A form, if the Case Product on the Transmission is a device, Vault now exports each device-type Case Product to a separate form. | SAF-102686 |
| For Product Quality Complaints (PQCs) sent to a Safety Vault through the Quality-Safety Connection, Vault does not copy Complaint Intake IDs on Case Assessments to follow-up Cases. | SAF-93502 |
| Vault does not map dates correctly to field 1.2c of EU MIR forms. | SAF-97928 |
| In Vaults using rules-based narratives that are not configured to isolate blinded clinical trial information, if the Product (Reported) is updated to the Product (Coded) during unblinding, the follow-up summary on the narrative document may include information for the unblinded Case Product. | SAF-100830 |
| When generating EU MIR forms, if the Onset date of the primary Case Adverse Event is blank, Vault populates field 1.2b with the Transmission Date instead of the Receipt Date. | SAF-102457 |
| When non-Vault Owner users run the Lock Inbox Item action from the All Actions menu, Vault displays a success banner, but does not load or refresh the page automatically. | SAF-103024 |
| When creating a follow-up from a closed Case, Vault opens the follow-up Case in the New state, instead of Revision, and assigns the incorrect Case Access Group. | SAF-103771 |
| In Vaults with the Sender-Based Inbound Validation setting enabled, Vault does not send an email or notification with a CSV rendition when an import fails due to a Validation Criteria with an invalid Rule Formula Format. | SAF-104311 |
Release Number: 26R1.0.5 | Build Number: N/A | Platform: N/A
| Description | Issue No. |
|---|---|
| In some instances, Workbench Dashboards filtered by a Case Series do not load. | SAF-102350 |
May 5, 2026
Release Number: 26R1.0.4 | Build Number: 212 | Platform: 10393
This release includes only Platform fixes.
May 1, 2026
Release Number: 26R1.0.3 | Build Number: 211 | Platform: 10385
| Description | Issue No. |
|---|---|
| This update optimizes code for standalone device Case Product export in E2B files. This will be available for configuration in a future release. | SAF-103779 |
|
In Vaults configured with an entry action for a custom Localized Case state upon case creation, when the workflow starts on a follow-up domestic Case or Localized Case, Vault moves the case to the configured state but then reverts it to the Active lifecycle state. |
SAF-104196 |
April 29, 2026
Release Number: 26R1.0.2 | Build Number: 208 | Platform: 10366
| Description | Issue No. |
|---|---|
| When a Safety Vault receives a follow-up Inbox Item from EDC, to support accurate due date calculations, Vault now applies the New Info Date from the earliest Inbox Item in the "Marked as Follow-up (Not Current)" state to new related follow-up Inbox Items. | SAF-98930 |
| When a Safety Vault receives a follow-up Inbox Item from EDC, if the Significance value is Significant Follow-Up, Vault does not link the superseded Inbox Item to the follow-up Inbox Item. | SAF-93399 |
| In some cases, Inbox Items generated from imported or emailed files have blank Intake Format and Intake Method values. | SAF-101988 |
April 16, 2026
Release Number: 26R1.0.1 | Build Number: 200 | Platform: 10338
| Description | Issue No. |
|---|---|
| The Safety-EDC Connection does not populate the Gender field on the CDMS Subject Pregnancy Child object and Vault generates a User Exception Item when the connection transfers that data. | SAF-101717 |
| Vault does not generate the Potential Matches Results CSV log when a user promotes an Inbox Item to a Case from the Potential Matches page and does not have permission to edit Transmissions. | SAF-101656 |