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 26R2 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 26R2.0, so our maintenance releases for this version are 26R2.0.2, 26R2.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 26R2 Maintenance Releases.
Last Updated: August 28, 2026
August 28, 2026
Release Number: 26R2.0.6 | Build Number: 273 | Platform: 10781
| Description | Issue No. |
|---|---|
| When a Web Intake Form respondent navigates from the summary page back to edit the Product page, the Product Name drop-down is expanded. | SAF-117949 |
| When running duplicate detection from a Case, Vault incorrectly categorizes Cases on which Case Adverse Events were added after promotion as ID matches when no matching identifiers exist. | SAF-118531 |
| Vault does not import documents attached to Web Intake Forms with file names exceeding 100 characters, and the form displays the file names outside of page margins. | SAF-118805 |
| When the New Info Date on an Inbox Item is populated with a single digit for the Day value (YYYY-MM-D), the New Info Date does not display on the Inbox Item object record list page. | SAF-119383 |
| Vault maps data incorrectly to a number of fields when generating PMDA Medical Device & Regenerative Medicine Forms in either PDF or XML format. | SAF-120792 |
| Users may experience slower than expected performance when generating CIOMS I forms in bulk. | SAF-120794 |
| When a Safety user promotes or merges an Inbox Item generated by the Safety-EDC Connection that has blinded and unblinded products, Vault syncs the Link value on the blinded and unblinded Case Products, resulting in duplicate Link values for the Study Products. | SAF-120796 |
| When voiding a Case with a Transmission in the E2B ACK Warning state, Vault does not move the lifecycle state of the Case from Nullifying to Nullified. | SAF-120802 |
| Users with permissions for global Cases but not Localized Cases cannot view or update the Patient ROA and Dose Form fields in the Dosages section of External Products if the data is mapped from the Localized Case. | SAF-120803 |
| When coding External Products to Localized Case Product records using WHODrug Global Chinese data, if the generic name does not include Chinese characters, Vault does not append the expected Chinese characters to the Generic Name value. | SAF-120804 |
| When autocoding Products during Case promotion, Vault does not apply WHODrug codes to Products with no Country Obtained value. | SAF-120834 |
| When promoting Inbox Items generated through the Safety-EDC Connection, Vault does not correctly match constituents of Combination Products on the Inbox Item to Case Compare page due to shared Link values. | SAF-121266 |
August 24, 2026
Release Number: 26R2.0.5 | Build Number: N/A | Platform: N/A
| Description | Issue No. |
|---|---|
| In rare instances when processing a high volume of data, the Signal EBGM service restarts unexpectedly, resulting in scheduled Signal Calculation failures. | SAF-119904 |
August 19, 2026
Release Number: 26R2.0.4 | Build Number: 255 | Platform: 10708
| Description | Issue No. |
|---|---|
| When generating safety reports from a Case Collection using the "Generate CIOMS I Unmasked Collection" record action, Vault populates the Blind Protection field incorrectly, resulting in blinded forms being added to "CIOMS I PII Unmasked & Study Unblinded" Case Collection types. | SAF-116055 |
| On NMPA E2B(R3) files, when the Patient RoA TermID and Patient RoA TermID Version on the Case Product Dosage do not map to an EDQM term, Vault populates the G.k.4.r.10.2a and G.k.4.r.10.2b data elements, instead of populating the G.k.4.r.10.1 data element, resulting in NACKs from the NMPA. | SAF-117379 |
| On Report Sets with required filters but no additional filters, Vault prevents saving Reports if users attempt to add a Case Series to them. | SAF-120610 |
| When importing an Inbox Item using the Intake API (v26.2), Vault generates an empty record with an import error. | SAF-120791 |
| In Vaults with the Enable Sender-Based Inbound Validation setting enabled, Vault sends multiple acknowledgments (ACKs) for a successful E2B import. | SAF-120981 |
August 13, 2026
Release Number: 26R2.0.3 | Build Number: 248 | Platform: 10683
This release includes only Platform fixes.
August 9, 2026
Release Number: 26R2.0.2 | Build Number: 247 | Platform: 10649
| Description | Issue No. |
|---|---|
| Users with View Document and View Content permission on an E2B XML file cannot generate an E2B Readable Rendition for that file. | SAF-119968 |
| Vault does not import documents attached to Single Use types of Web Intake Forms and attach them to the generated Inbox Item. | SAF-120087 |