Veeva CRM Sandbox - Salesforce Winter '27 Release Issues
Veeva CRM Sandbox - Salesforce Winter '27 Release Issues
August 30 2026,12:00pm PDT
August 30 2026,12:00pm PDT
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.
August 31 2026,7:32pm PDT
August 31 2026,7:32pm PDT
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.
September 01 2026,4:01pm PDT
September 01 2026,4:01pm PDT
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.
September 02 2026,9:32am PDT
September 02 2026,9:32am PDT
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.
September 03 2026,12:02pm PDT
September 03 2026,12:02pm PDT
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."
September 04 2026,8:27am PDT
September 04 2026,8:27am PDT
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.
September 08 2026,9:58am PDT
September 08 2026,9:58am PDT
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.