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: September 18, 2026
September 18, 2026
| Description |
Issue No. |
|
Due to a caching issue, in some instances, CIOMS I form generation fails for Cases with Combination Products that include Product Registrations with a PMOA value.
|
SAF-124499 |
September 16, 2026
| Description |
Issue No. |
|
For Inbox Items merged to in-flight Cases via the Inbox Item to Case Compare page, Vault does not consider the Indication under the Case Product when evaluating expectedness.
|
SAF-119869 |
|
In some instances, when populating Localized Case Product Substance records for External Products coded using the Korea Drug Dictionary, Vault does not map the correct Korean Substance Name for the English Substance Name.
|
SAF-121446 |
|
When users who have submitted more than 500 Repeat Use type Web Intake Forms complete email reverification, a "Page Not Found" error displays instead of the form.
|
SAF-123783 |
|
Vault does not import attachments for imported E2B(R3) files with attachments exceeding 20M characters.
|
SAF-123888 |
September 11, 2026
| Description |
Issue No. |
|
When mapping CTA Approval Numbers from active Study Products related to Case Products, Vault now lists the CTA Approval Number of the Study Product related to the Study on the Case first in the comma-separated list of numbers.
|
SAF-121039 |
|
When Safety Reporting Service downtime occurs, Workbench Reports in the In Progress state stop processing and remain in that state.
|
SAF-118823 |
|
Following Case unblinding in Vaults configured to isolate clinical trial information, if a user unblinds a Study Product by selecting a Product and populating the Product (reported) field, Vault maps the Product (reported) value to the blinded record.
|
SAF-119099 |
|
When a user deletes a Case Adverse Event for a follow-up Case, the Summary Statement output for the regenerated rules-based narrative includes an extra statement with details about the removed event.
|
SAF-121013 |
|
When a user adds a Case Adverse Event for a follow-up Case, the Summary Statement output for the regenerated rules-based narrative includes a statement with details about the related new Case Assessment and Case Assessment Results.
|
SAF-121014 |
|
In Vaults using the Safety-RIM Connection, users experience slower than expected performance when running some actions, including Generate E2B Readable Rendition.
|
SAF-121102 |
|
After running a Workbench Dashboard filtered on a custom MedDRA query (CMQ) with Narrow as the scope, Vault displays an error, instead of returning zero cases, if none of the terms in the CMQ has Narrow as the Scope.
|
SAF-121225 |
|
After running the Merge Binder to PDF action on a Case Collection, Vault does not notify users of successful completion nor add links to download PDFs through the notification bell icon.
|
SAF-121826 |
|
On generated August 2024 and September 2025 versions of FDA MedWatch 3500A forms for which the Transmission specifies a Case Product, Vault populates the Remedial Action Other text for all Case Products in section H7.
|
SAF-122366 |
|
In Vaults using the full ICH E2D(R1) study types list, for ICH E2D codes 4, 5, and 6, Vault populates E2B code 2 (Individual Patient Use) instead of 1 (Clinical Trial) in the G.k.9.i.2.r.2.KR.1 data element of MFDS E2B(R3) files.
|
SAF-122431 |
September 4, 2026
| Description |
Issue No. |
|
CIOMS I forms generated from Case Collections with the "CIOMS I PII Masked & Study Blinded" Case Collection type do not mask PII fields.
|
SAF-122847 |
September 2, 2026
| Description |
Issue No. |
|
If a user manually deletes Local Reporting Details records on a Localized Case, Vault does not automatically delete the related Localized Case Comment records, which prevents subsequent creation of follow-up Localized Cases.
|
SAF-116639 |
|
For users with access to Case Products but not Case Product Dosages, blinded study Cases assessed as SUSARs display as blank pages.
|
SAF-120682 |
|
During assessment generation, a server error appears in the Case Assessment, Case Assessment Results, and Case Assessment Expectedness sections of Cases.
|
SAF-120751 |
|
In some instances, Repeat Use type Web Intake Forms are not accessible to form respondents due to out of sync verification tokens.
|
SAF-121047 |
|
In Vaults using the Safety-RIM Connection that have a Veeva SafetyDocs license only, and no Veeva Safety license, the Reprocess Request Action is not available to run on User Exception Messages.
|
SAF-120674 |
August 28, 2026
| 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
| 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
| 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
This release includes only Platform fixes.
August 9, 2026
| 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 |