---

Every Salesforce release brings hundreds of changes, but only a handful will touch your daily work. This guide filters the Salesforce Winter ’27 release down to what matters for admins and developers: the Flow Builder overhaul, higher Apex limits, reporting and permission improvements, and — most importantly — the release updates that enforce whether or not you act on them.

Winter ’27 is a build-and-test release for automation. Flow Builder gets its biggest visual and functional refresh in years, Apex gains real headroom on heap, and a cluster of security release updates continues Salesforce’s multi-year push to retire legacy authentication. Just as important is knowing what didn’t land this cycle: a few widely reported items were postponed or removed before general availability, and getting those dates right saves you from testing the wrong thing.

What the Salesforce Winter ’27 Release Means for Admins and Developers

A Salesforce release rolls out to every org whether you prepare for it or not, but the impact is uneven. Most features are additive and optional — you adopt them when you’re ready. A smaller set of changes, called release updates, enforce on a fixed schedule and can break existing automation or integrations if you ignore them. The single most valuable habit each cycle is separating the two.

For Winter ’27, the “must act” list is short. Two behavioral release updates are enforced this release: Enable Profile Filtering and Assign Use Any API Auth Permission for SOAP login(). The rest of the enforced items are accessibility enhancements. Several security release updates that circulated as “Winter ’27 breaking changes” were actually postponed — the OAuth 2.0 username-password flow retirement now enforces on February 20, 2027, not this release. We cover the full enforcement schedule in the release updates section below.

The best way to prepare is a sandbox on a preview instance: test your customizations and walk the Release Updates node before your production upgrade weekend. Start with the updates that change behavior, then evaluate the new Flow, Apex, and reporting features on this page.

Flow and Automation Upgrades

Flow Builder receives its most substantial update in several releases — a mix of a visual refresh, genuine time-savers, and one long-requested capability that removes a whole category of custom code. With Workflow Rules and Process Builder having reached end of support on December 31, 2025, Flow is the go-forward automation tool, and Salesforce is investing accordingly.

Run screen flows against multiple records at once GA

You can now run a screen flow as a mass quick action from a list view or related list, so it fires once against every record a user selects instead of once per record. This is the item admins have requested across multiple cycles, and it removes the need for a custom list-view button or a small Apex controller just to bulk-update a handful of fields. If you built that workaround, this release is the moment to check whether the native action can replace it.

Split by Date and Split by Field Value GA

Two new Decision types let you route records based on common conditions without writing expressions. Add a Decision element, choose Split by Field Value to branch on a field, or Split by Date to branch on the current date, then define your paths with inline pickers. It’s a small change that lowers the expertise needed to build branching logic.

Flow Test Mode Beta

Flow Builder now separates Build and Test modes, giving you one place to debug and save reusable test scenarios for record-triggered and autolaunched flows. You can save standardized scenarios for regression testing before pushing changes live, and test flows in isolation using mock outputs for Action and Subflow elements. This is the closest Flow has come to a real testing framework — treat it as beta and validate in a sandbox.

A denser, modernized canvas GA

Flow Builder adopts the modern Salesforce Cosmos theme (part of the Salesforce Lightning Design System 2), automatically matching your org’s active theme. The canvas is more compact so you see more of your flow without scrolling, element cards surface the element type and API name in an info tooltip, and the End element is now a simple icon rather than a full card. One caveat worth noting: Flow Builder does not support SLDS 2 Dark Mode.

Edit History and organization tools GA

For flows that support versioning, Edit History shows a timeline of every save so you can preview what changed, restore previous logic, create a new version from a past save, or copy logic into a different flow. Alongside it: auto-generated element labels, collapsible element Groups to organize complex flows, an Unused Resources filter in the Toolbox to find and remove clutter, clearer Decision element navigation, and keyboard shortcuts for moving around the canvas and cutting, copying, and pasting elements.

Run a flow in the context you intend GA

A new run context option, User Context — Enforces User Permissions, guarantees that a flow always runs with the running user’s access level regardless of what launches it. It’s available for screen flows and autolaunched flows and closes a common security gap where a flow ran with more access than the user should have had. This is exactly the kind of behavior worth understanding for record-level access design; if you build record-triggered automation, our guide to record-triggered flows in Salesforce covers where these run in the order of execution.

Error handling that catches problems earlier GA

Winter ’27 moves several failure modes from run time to save time. Flow Builder now catches field length violations when you save, flags missing required fields in Create Records elements before they fail, and can automatically retry flows that hit record lock contention. Fewer surprises in production. Rounding out the release: a new Time screen component for capturing time values, reactive formulas usable in conditional visibility rules on screens, and a Request Approvals component that adds up to 10 flow approval processes to a single record page.

Apex and Developer Enhancements

The developer story in Winter ’27 centers on one headline number and a set of quality-of-life improvements for testing and managed packages.

Higher Apex heap limits GA

The Apex heap limit for synchronous transactions increases from 6 MB to 10 MB, and the limit for asynchronous transactions increases from 12 MB to 25 MB. That’s meaningful headroom for jobs that process large datasets or build big in-memory collections, and it reduces a common class of runtime limit errors. The increase applies automatically once your org upgrades. For the full picture of how heap fits alongside SOQL, DML, and CPU caps, see how these interact in Apex governor limits and the asynchronous Apex tiers.

Better testing tools Beta / DP

Two additions target the parts of Apex development that have always been awkward. Elastic limits — which let jobs continue past the standard rolling 24-hour asynchronous limit — now extend to Batch jobs, in addition to future methods and Queueable (beta). And a new developer preview lets you write Apex integration tests that call real HTTP endpoints without mock callouts, using the new @BeforeClass annotation to share test data across methods in an integration test class. You can override the async job limit in a nonproduction org to see how elastic processing behaves before enabling it in production.

Managed package and API changes GA

If you build managed packages, Winter ’27 resolves a long-standing annoyance: when a package field and a subscriber’s custom field share a name, SOQL results could be ambiguous. Set the explicitNamespace property on a Database.QueryOptions object and pass it as a bind variable in the SOQL SET OPTIONS clause to declare exactly which namespace’s field you want. Also new: the Apex Symbol API (beta) exposes detailed type metadata through the Tooling API for building IDE tooling or grounding AI code assistants, you can recompile only invalid Apex classes and triggers instead of the whole org, and the Test Discovery API’s testLevel parameter replaces showAllMethods in API version 68.0.

Query, API, and tooling quality-of-life wins GA Beta

Several smaller changes round out the developer experience. The new FORMULA() function lets you perform arithmetic and compare values between fields directly in a SOQL WHERE clause (beta) — no more creating a formula field just to filter on a calculation. REST API version management gets simpler too: use latest in place of a numbered version in a REST URI (for example, /services/data/latest/sobjects/Account) to route automatically to the most recent version your org supports. Salesforce CLI can now scaffold asynchronous Apex classes with built-in best practices through the Batchable and Queueable values of the --template flag, generating strongly typed, compile-checked skeletons. And for AI-assisted development, an official Claude Code plugin for Salesforce and Salesforce Skills for coding agents are now available to build apps faster from the command line.

Lightning Components, App Builder, and API

The front-end and platform layer gets a batch of items that graduate to general availability plus a few admin-facing conveniences.

In Lightning Web Components, complex template expressions and Third-Party Web Components are now generally available, you can call the refresh() action for state managers to refetch data more easily, and LWC moves to API version 68.0. In Lightning App Builder, you can expose the standard Follow button on Dynamic Highlights Panels, letting users subscribe to updates on key records without a custom component.

On the API side, version 68.0 brings admin control over guest user access to the GraphQL API, a Metadata API field for managing the Automation Lightning App preference, and the API Catalog for centralizing services — including registering and activating MCP servers for use with Agentforce. One deprecation to note for integration owners: Salesforce Platform API versions 31.0 through 40.0 are slated for deprecation in Summer ’27 and retirement in Summer ’28, so audit older integrations now.

Reports and Dashboards

Reporting improvements in Winter ’27 are modest but practical. The standout for everyday users is Preview Records from Lightning Reports (beta): click the eye icon in a report to open a record in a side panel and move between records without leaving the report — your filters, columns, and record list stay intact. Enable it under Reports and Dashboards Settings. Also in beta, you can embed Lightning reports and dashboards in LWR-based Experience Cloud sites using native Lightning web components, so community users can view, filter, refresh, and even edit records inline without leaving the site.

On the Data 360 reporting side, joined reports make it easier to compare related data across sources to surface cross-object insights, you can compare converted currency values consistently across regions, and customer sentiment trends can sit alongside business data. If your reporting leans on joined reports or cross-object analysis, these are worth a look in preview.

Permissions, Sharing, and Setup

Several changes in this area are quiet but genuinely useful for day-to-day administration.

Keep manual shares on ownership transfer GA

You can now choose whether to keep manual shares when you transfer a record’s ownership. Previously, reassigning an owner could silently drop manually granted access; now that behavior is a deliberate choice. It’s a small setting that prevents a frustrating class of “why can’t they see this record anymore” tickets.

Security Health Review, now interactive GA

Security Health Review replaces the old PDF-only export with an interactive report viewer built into Setup. You get a continuous view of your org’s security posture with findings management, remediation tracking, disposition workflows, and a full audit trail of every report and action — a far more workable way to run security reviews than a static document.

Also new in this area: a dedicated View Setup Audit Trail permission (a release update enforcing in Spring ’27) that lets you grant audit-trail access without the broader View Setup permission. And inline editing in list views becomes more flexible — two new User Interface Settings let users edit any field they have access to whether or not it’s on the page layout, and allow inline editing in list views that contain multiple record types.

Agentforce for Admins and Developers

Agentforce is a large theme in Winter ’27, but a few changes stand out for admins and developers regardless of how deep you’ve gone with agents. The Agentforce platform is now enabled by default for all orgs with Agentforce access — new orgs are enabled at creation, existing orgs are auto-enabled on a rolling basis, and the enablement setting is removed from the Agentforce Agents page in Setup. There’s no additional cost and no billing change.

For developers, moving agents between orgs gets dramatically simpler. Starting in API version 68.0, the new AiAgentDefinition and AiAgentDefinitionVersion metadata types let Salesforce CLI retrieve an agent and all its dependencies automatically — previously, moving an agent from sandbox to production required at least three metadata types plus manually tracking every associated Apex class, flow, and prompt template. One date to calendar: the Gemini 2.5 Pro, Flash, and Flash-Lite models will be rerouted to Gemini 3.5 on October 20, 2026, so test your prompts against the new models in Prompt Builder before then.

Release Updates: What to Act On in the Salesforce Winter ’27 Release

This is the part of the release that enforces whether or not you prepare. The table below separates what’s enforced now from what’s coming, with the enforcement dates that matter. Review each one from Setup under Release Updates, and note that the OAuth authentication retirements — widely reported as Winter ’27 changes — were postponed and now land in 2027.