Winter ’27 is Salesforce’s autumn 2026 release, and it reaches production orgs in stages through early October. Salesforce’s release notes run to hundreds of items. A working admin needs a few dozen of them at most, and most of those sit in Flow and in the five release updates that Salesforce enforces with this release.
This guide sorts Winter ’27 by what changes your week: the Flow features worth testing first, how mass quick actions for screen flows behave and where they stop, the enforced release updates to check, and a short verification routine for the days after your org upgrades. Admins who want an AI client to do some of the reading can see how Cirra AI works for Salesforce admins.
Salesforce and community sources list slightly different weekends for the production upgrade, so confirm your instance’s window on trust.salesforce.com before you plan around it. The details below come from Salesforce’s own announcements and from the admin community’s reading of the release notes. Check each feature against the official notes for your edition before you build on it.
What is Winter ’27, and which parts do admins need?
Salesforce ships three major releases a year. Sandboxes on the preview schedule get Winter ’27 first, which gives you a few weeks to test your automation on the new version before production changes.
Three parts of the notes deserve a full read: Flow, release updates, and the Setup and reports sections. Sales, service and marketing features are product decisions for the business teams. The admin sections are where an upgrade can change how your existing configuration behaves.
Flow features worth testing first
Flow is where most admin teams spend release week, because a change to how flows run touches live processes. Here are the Winter ’27 items that change what you build or maintain.
Mass quick actions for screen flows
A user can select records in a list view and launch one screen flow against all of them. Salesforce passes the selected record IDs into the flow as a variable, so you no longer need custom Apex or Visualforce for a bulk action. The flow opens in a modal.
Setup is picky. Create a text collection variable with the API name ids, check Allow Multiple Values and Available for Input, then add a Quick Action of type Flow on the object and place it on the list view button layout. A variable named recordIds or selectedIds produces a flow that starts normally, finds an empty collection and updates nothing.
The limits decide whether the feature fits your use case:
- The UI accepts up to 2,000 selected records.
- Each screen is a transaction boundary, and the transaction gets the usual 10 seconds of CPU time, 100 SOQL queries and 10,000 DML rows.
- Triggers, record-triggered flows and validation rules on the target object use that same CPU budget.
- DML is all-or-nothing, so one validation failure rolls back every record in the run.
- There is no undo, and it works in Lightning Experience only.
The 2,000 figure is the UI ceiling. Your org’s automation weight sets the practical one. A Case object whose automation burns a second per chunk of records will hit the CPU limit well before 2,000. Build a fault path that tells the user which record failed, and test with a realistic selection size in a sandbox. If your volume is regularly in the thousands, a scheduled flow or a batch Apex job is still the better tool.
Flow Test Mode and the enhanced debugger
Flow Test Mode is in beta. It gives record-triggered and autolaunched flows a dedicated workspace where you set the triggering record, choose paths, define assertions and save the scenario so you can rerun it with one click. A related beta lets you mock the output of an Action element, so a test run skips the real REST request and returns a response you defined.
The debugger also gained static 15 or 18 character record IDs for objects with limited searchability, and it can populate primitive and record collections for multi-record testing.
Use these tools on your fault paths on purpose. Force a bad value into a test and watch where the flow goes. A fault path that has never run is a guess.
Error prevention at save time
Flow Builder now warns you at save time when a Create Records element that uses a record variable is missing a required field. It also warns when a fixed-text assignment is longer than the target field allows. The field length check does not cover values that come from variables, so dynamic text can still fail at runtime.
Two runtime changes help in production. Scheduled flows can use dynamic batch sizing, which retries with half the batch size when a CPU, SOQL or heap limit is hit. And when a flow hits an UNABLE_TO_LOCK_ROW error during initialization, it pauses for 10 seconds and retries.
Housekeeping in Flow Builder
Several smaller items make a large flow library easier to run. The Edit History panel shows a timeline of saves and lets you preview what changed in each one. An unused resources filter in auto-layout mode lists variables, collections and formulas that nothing references. Flow Tags let you classify flows and filter by tag. A new runtime setting, User Context Enforces User Permissions, makes a flow respect the running user’s object, field and sharing permissions.
The five enforced release updates
Release updates are changes that Salesforce lets you enable early and then switches on for every org on a set date. Winter ’27 enforces five, according to SalesforceBen’s pre-release guide:
- SOAP API authentication. Users without the Use Any API Auth user permission can no longer authenticate through the SOAP API login() call.
- Card and container accessibility. Cards, docked containers, menu lists and panels adapt to magnification above 200%.
- Date picker and header accessibility. The same magnification behavior applies to date pickers, popovers, utility bars and record headers.
- Modal and page header accessibility. Modals and page headers get the same treatment.
- Profile filtering. Users can no longer see profile names other than their own unless they hold the View All Profiles permission.
The first and last items can break things people rely on. An old integration that still calls SOAP login() will fail for any user who lacks the permission, and a custom page or report that shows another user’s profile name will go blank for users without View All Profiles.
To check your own list, search Setup for Release Updates, sort by enforcement date and test each open item in a sandbox. Record the result next to the update name so the next admin knows what was covered.
A verification routine for the days after your upgrade
A release rarely breaks things loudly. The failures that cost time are quiet: a flow that stops firing for one record type, an integration that gets a new error, a report that loses a column.
- Pick the ten automations your revenue or support depends on. Include flows, validation rules and approval processes.
- Run each one in the preview sandbox and compare the results with what you saw before the release.
- List your SOAP API integrations and confirm that each integration user holds Use Any API Auth.
- Check the flow error email recipient. Salesforce sends fault emails to the person who last saved the flow, and that person may have left.
- Sample real records after your production upgrade. Open five records on each key object and confirm that the automation updated them as expected.
Where Cirra AI fits
Much of the prep above is reading and comparing: which flows touch which objects, which integration users lack a permission, which validation rules sit on an object. Cirra AI is a Salesforce Admin MCP Server. It connects the AI client you already use, such as Claude, ChatGPT or Cursor, to your org, and it reads your metadata through the Tooling and Metadata APIs.
You can ask for every active flow that updates Case records, or for the permission sets that include a given user permission, and review the answer in the same chat. When you decide to make a change, such as adjusting a validation rule or a permission set, Cirra AI makes it as the connected user, within that user’s permissions, and documents it. You test the change in a sandbox and promote it through your usual process.
The Salesforce Admin MCP product page lists what it can read and change. If you are still choosing a client, the guide to connecting Claude to Salesforce walks through setup.
FAQ
When does Winter ’27 reach my org?
Sandboxes on the preview schedule receive the release first, and production orgs follow in waves over release weekends in early October 2026. The date depends on your instance, so check trust.salesforce.com for your window.
What are mass quick actions for screen flows?
They let a user select up to 2,000 records in a list view and run one screen flow against them. Salesforce passes the record IDs into a text collection variable named ids. The run is all-or-nothing and shares the transaction’s 10-second CPU limit with any automation on the object.
Is Flow Test Mode generally available?
Salesforce’s Winter ’27 notes mark Flow Test Mode and mock outputs as beta features. Use them in sandboxes and confirm the status in the release notes before you rely on them for your release process.
What is a release update in Salesforce?
A release update is a change to platform behavior that you can enable early and that Salesforce enforces on a set date. You find them in Setup under Release Updates.
Which Winter ’27 release updates are most likely to break something?
SOAP API authentication and profile filtering change who can do what. Users without Use Any API Auth can no longer log in through the SOAP API, and users without View All Profiles lose sight of other users’ profile names. The three accessibility updates change layout behavior at high magnification.
Can an AI client help me prepare for a Salesforce release?
It can help with the reading and comparison work. Cirra AI connects an AI client to your org’s metadata, so you can ask which flows, validation rules and permission sets touch a given object and review the answer. Changes run as the connected user within their permissions, and you should test them in a sandbox first.
