Veeva outage history

Veeva Compass is currently experiencing a delay in today’s daily job processing. As a result, recurring daily jobs will run later than their scheduled start times. Our engineering teams are working to resolve the issue. A Trust update will be posted once daily jobs are initiated.

The processing delay impacting Veeva Compass daily jobs has been resolved. All delayed recurring daily jobs have now completed, and daily job processing is operating normally.

Veeva Vault POD VV1-1217 is currently experiencing intermittent degraded performance. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva Vault POD VV1-1046 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva Vault POD VV1-4022 is currently experiencing intermittent degraded performance. Veeva engineering teams are working to return the service to normal as quickly as possible.

Veeva Vault POD VV1-4022 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.

The service disruption on Veeva Vault POD VV1-4022 is resolved and services are performing normally. Veeva engineering teams will continue to monitor performance as the expected load increases.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Salesforce is currently experiencing an outage affecting Veeva CRM. Users attempting to login will experience login failures with an internal server error. Offline mode on iOS will still allow for the creation of calls and displaying media, however, sync and online functionality is not available. For the latest information, please follow Salesforce's incident at https://status.salesforce.com/incidents/20004433

Salesforce has identified the issue and are actively deploying a fix across the impacted instances to restore services.

Salesforce are continuing to see healthy service telemetry and there is one isolated report left to validate before declaring resolution. Affected PODs are now fully available with all services operating normally.

Veeva Compass is experiencing a delay in today’s daily data processing and estimated time to process is currently undetermined. As a result, customer daily jobs will remain on their current schedule and there will be no new network data additions for today, Friday September 4th. Veeva engineering teams are working to return the service to normal as quickly as possible.

Veeva Vault POD VV1-11 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva Vault POD VV1-11 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva Vault POD VV1-11 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.

We are still working on the issue.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva Vault POD VV1-11 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible. Users may have experienced issues related to document and object record loading in Vault up until 9:35 AM PDT following the resolution of the outage. But that issue is also resolved now.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva Vault POD VV1-11 is currently experiencing a service disruption. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Veeva CRM team has noticed that some users are unable to login on Sandbox orgs and/or use Multichannel activities like Approved Email.. This is due to Salesforce's Winter '27 update. Veeva has raised a ticket with Salesforce to address this issue.

We are continuing to work with Salesforce to resolve the issue introduced with their Winter ’27 release that is preventing users from logging in from iPad. Additionally, we have identified another issue affecting users in Sandbox, where some buttons are missing from the Account page. Salesforce has confirmed that this issue is also related to their Winter ’27 release, and we are actively working with them to resolve it.

We are continuing to work with Salesforce on this issue. Salesforce is looking at why different Orgs are behaving differently when attempting to use the Soap API. For users that need to login to an iPad , you can select the "Use Custom Domain" from the login screen. As we continue to work with Salesforce to investigate this issue, we have identified a solution that has been successful in some Salesforce orgs for Integration Users. Salesforce provides additional information on the relevant API authentication permission here: Salesforce Developers Create a new permission set with the Use Any API Auth system permission enabled, and then assign that permission set to the affected user. Please note that the Use Any API Auth permission is only available when the permission set is created with the License value set to None . In some Salesforce orgs, assigning the permission set may fail with the following error: "Can't assign permission set test_permission_set2 to user Veeva Admin. The user license doesn't allow the permission: Use Any API Auth" We have observed that this workaround can be applied successfully in some orgs but not others, even when the affected users have the same license type. We are continuing to work with Salesforce to better understand the difference in behavior across orgs.

We have identified an unplanned UVC resulting from the Salesforce Winter ’27 release. Salesforce has confirmed that this behavior is unexpected and plans to publish a Known Issue within the next day. Salesforce has confirmed: “We’ve confirmed there’s a regression where existing sandbox orgs upgraded to Winter ’27 are unexpectedly switching from the Lightning Blue theme (SLDS 1) to the newer Salesforce Cosmos theme (SLDS 2). This is happening even without any admin action.” We will continue working with Salesforce on a resolution. In the meantime, Admins can change the theme setting back to SLDS 1 to restore the expected UI experience.

Salesforce has provided an additional update on the Cosmos theme. Unfortunately, changing the Theme back does not resolve the issues. We are continuing to work with Salesforce on a resolution. From Salesforce: "At this time, we don't have an alternative workaround to offer for orgs where the theme is already correct and non-adjustable. We understand this is impacting your customer's business processes, and we're treating this as a priority given the number of affected customers. We don't have a fix ETA yet, but we'll continue to push for updates and will let you know as soon as we have more concrete guidance including whether a documented Known Issue will be published."

Update on the current status for Winter ’27 Salesforce release issues in Sandbox 1. UI Theme Regression — Lightning Blue (SLDS 1) switching to Cosmos (SLDS 2) Salesforce has confirmed their provided workarounds do not fully remove Cosmos UI/functionality changes in Sandbox Orgs. They are working on a fix to resolve this in Sandboxes. In Production Orgs, Salesforce has confirmed they will NOT deploy the Cosmos UI as auto on so this will not affect Production Orgs, however, they continue to review methods to fix Sandboxes. 2. Missing Buttons on the Account Page This is now resolved. We were able to have Salesforce speed up their release date and a fix was deployed last night/this morning to resolve the issue. Some Orgs may still be receiving the fix, however, the majority of Orgs are updated and many customers have already have confirmed the issue is resolved. This is also documented here: Salesforce Known Issue – a02g7000008RQjN 3. Sandbox Login Issues and SOAP API / Integration User Authentication Behavior In Sandbox Orgs, Customers will still need to apply the permission set changes described in earlier posts and if those fail, reach out to Support for an additional manual step that is needed to fully resolve the permission set behavior. In Production Orgs, the Veeva CRM team will be releasing changes to ensure these manual steps are NOT needed in Production (this will also resolve any Sandbox Orgs that haven’t been manually). There may be steps needed by customers, however, this would be a one-time Org change not a permission set per user. Please open support cases if you have additional questions or follow our Connect Post .

This weekend Salesforce rolled out a fix so the "Use Any API Auth" permission is not needed in Sandbox. All users and integrations should now be working as expected without any further manual changes.

Vault CRM team has noticed that Conversational AI is unavailable to users. Engineering is investigating the issue.

A fix has been identified and will be deployed shortly.

Incident has been resolved

Vault CRM i s currently experiencing intermittent degraded performance when sending Approved Emails. Emails are not immediately sending and moving to the Saved status. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Vault CRM services are now fully available with all emails processing normally.

Veeva CRM team has noticed a small percentage of Email Activity is delayed. Engineering is investigating the issue.

Veeva RegOne + Claims Release Notification The RegOne + Claims MySQL system is scheduled to be upgraded to the latest release. There is no expected downtime however, a short service interruption may be experienced. What: MySQL 26R2.0 When: August 4 at 7:00 pm PDT/August 5 at 4:00 am CEST Estimated Duration: 90 minutes Affected PODs: General Release PODs Click here to learn how to find your Vault's POD location. For up-to-date information on Veeva Systems' service status, see the Veeva Trust Site . If you have any further questions, please submit a ticket with Veeva Product Support .

This informational post is closed. The upgrade was successful as planned and completed on August 4.

Veeva Vault POD VV1-1090 is currently experiencing intermittent degraded performance. Veeva engineering teams are working to return the service to normal as quickly as possible.

Affected Veeva Vault PODs are now fully available with all services operating normally.

Investigating: SSO Login Failures Across some Vault Environments Issue Summary: We are currently investigating an issue where users are unable to log into Vault via Single Sign-On (SSO). This was caused by the new SSO Certificate being applied to Vault settings earlier than announced. (For reference, see Veeva Release Notes .) Immediate Workaround (Vault Admins): Vault Domain/System Administrators can restore user logins immediately by logging into Vault and reverting the Single Sign-On (SSO) Profile configuration back to the previous (old) certificate . Please reference https://rn.veevavault.help/en/gr/certificate-rollover/#rollback. We apologize for the disruption and will provide another update by 1:30 am PT as the engineering team is currently assessing if any further corrective action will be taken.

Latest Update: Our engineering team has completed their assessment, and no further action will be applied by Veeva. To avoid further disruption, the new SAML certificate will remain active on Vault configurations. Direct email communications have been sent regarding this incident and next steps. Restoring User Access (Immediate Workaround): Vault Domain Administrators can immediately restore login access for their users using one of two options: • Option 1 (Complete Transition): Update your Identity Provider (IdP) configuration to trust the new SAML certificate . This will align your IdP with Vault's active setting and permanently resolve the issue. • Option 2 (Revert Vault Setting): Log into Vault using local/non-SSO credentials and manually revert the SAML Profile configuration back to the previous (old) certificate under Admin > Settings > SAML Profiles . Detailed instructions and guidance remain available in Vault Help . If you are an administrator requiring login assistance or support with your SAML configuration, please submit a high-priority ticket with Veeva Product Support . We sincerely apologize for the disruption caused by this premature update. This ticket will be closed on 7/31 at 10:00 am PT.

Issue is closed.

Vault CRM Online functionality in the US Region are currently experiencing intermittent degraded performance. Offline devices will continue to work as expected, however, sync errors may occur and self resolve once the servers are healthy. Veeva engineering teams are working to return the service to normal as quickly as possible expecting to be resolved shortly

This issue is resolved. All US servers are working as expected

Veeva CRM team has noticed an increased amount of Multichannel jobs failing. Engineering is investigating the issue.

Incident has been resolved.