Must-Know New Salesforce Flow Features: What Changed Through Winter '27
Salesforce Flow has changed more in the last two years than in the five before. Screen flows gained action buttons, repeaters and reactive screen actions, approvals and orchestration moved into Flow, Workflow Rules and Process Builder lost support, and Winter '27 adds edit history, stricter permission control and a new way to test. Here is what is new, what is still beta, and what to adopt first.
Key Takeaways
- Winter '27, generally available since October 2026, is the current Salesforce release. Its Flow headlines are Edit History, element groups, a run mode that always enforces the user's permissions, automatic retry on record-lock errors, and Flow Test Mode (beta).
- Screen flows now behave like small apps: Action Buttons (generally available since Winter '25), the Repeater (generally available since Summer '24) and reactive screen actions (generally available since Summer '25) update a screen without moving to the next one.
- Approvals and orchestration now live in Flow. Flow Approval Processes arrived in Spring '25, and Flow Orchestration became a standard feature in February 2026, with no usage-based charge in the editions that include it.
- AI flow building is useful but not finished: Agentforce for Flow went back to beta in Summer '26, and Winter '27's Flow Author is also beta. Review every AI-drafted flow like a junior developer's work.
- Support for Workflow Rules and Process Builder ended on December 31, 2025. They still run, but nothing will be fixed. Migrate them to Flow, starting with the processes that matter most.
What are the new Salesforce Flow features? They are the changes Salesforce ships to Flow, its declarative automation tool, three times a year. Since mid-2024 those changes have rebuilt how flows are created, tested, versioned and secured. Screen flows gained interactive components, approvals and orchestration moved into Flow, AI can now draft flows, and the legacy tools Flow replaced are no longer supported.
We first published this post in 2023, when the news was a new creation wizard, unlimited paused flows, the Action Button beta and the Repeater. This version is rebuilt from Salesforce's release notes, Help documentation and the official Salesforce Admins blog, checked in October 2026, and covers every release from Summer '24 to Winter '27. It is written for Salesforce admins, architects and operations leaders at growing and mid-market companies who need to know which new Salesforce Flow features are ready to use, which are still beta, and what to change in their own org.
Which New Salesforce Flow Features Matter Most in 2026?
The features that change how reliable and maintainable your automation is, not the ones that look best in a demo. For most orgs that means migrating off Process Builder, moving approvals into Flow, using Edit History and version comparison, testing flows before they ship, and redesigning clunky multi-screen flows with action buttons and reactive screen actions.
| Feature | Release | Status | Why it matters |
|---|---|---|---|
| Repeater screen component | Summer '24 | GA | Users add several records (contacts, line items) on one screen |
| Unlimited paused and waiting flows | Summer '24 | GA | No per-org cap on paused interviews; only storage limits them |
| Action Button | Winter '25 | GA | Runs an autolaunched flow and shows the result on the same screen |
| Flow Approval Processes | Spring '25 onward | Available | Salesforce's replacement for classic approvals, built in Flow |
| Reactive screen actions | Summer '25 | GA | Screens fetch and calculate data as users type or select |
| Version comparison | Winter '26, extended in Spring and Summer '26 | Available | See exactly what changed between two flow versions |
| Flow Orchestration as a standard feature | February 2026 | Standard | Multi-step, multi-user processes without a paid add-on |
| Edit History, element groups, Unused Resources filter | Winter '27 | New | Large flows become easier to read, audit and roll back |
| Flow Test Mode, Flow Author | Winter '27 | Beta | Reusable test scenarios; AI-generated flows. Pilot, do not depend on |
Edition availability differs by feature, and many screen components are not supported in the Classic runtime. Check the release note for each feature before you plan around it. Salesforce's own Winter '27 automation release notes are the place to start.
What Is New in Salesforce Flow in Winter '27?
Winter '27 is a maintainability and safety release for Flow. It adds a full edit history, collapsible element groups, a permission-enforcing run mode, record lookups in a collection without a loop, automatic retries on record locks, and screen flows that run from list views. Salesforce announced general availability on October 12, 2026, and the release ships with API version 68.0.
Edit History
For flows that support versioning, a timeline of every save. Preview an earlier save, see element-level detail, restore it as a new version, or copy its logic into another flow.
Element groups and cleanup
Group elements into named, collapsible sections, filter the Toolbox for unused resources, and let Flow Builder suggest element labels. Keyboard navigation and cut, copy and paste arrive too.
User context that enforces permissions
A new run option, User Context (Enforces User Permissions), for screen and autolaunched flows on API version 68.0 or later. The flow always respects the running user's object access and sharing, whoever calls it.
Find a record without a loop
A Collection Filter Criteria resource returns the first matching record from a collection, so a Loop and Decision pair is no longer needed just to find one record.
Retry on record locks
When a flow hits an UNABLE_TO_LOCK_ROW error as its transaction starts, it now waits 10 seconds and tries again. New save-time warnings also flag unmapped required fields and values too long for their field.
Screen flows from list views
A mass quick action on a list view or related list can launch a screen flow that receives every selected record ID. A new Time screen component accepts minimum and maximum values.
Two other changes are worth knowing. Decision elements gain Split by Date and Split by Field Value options that route records without writing conditions, and the Contains operator now works on multi-select picklists in Get, Update and Delete Records. The canvas also shows flow performance data for most flow types, and Flow Builder adopts Salesforce's Cosmos theme. Salesforce removed several planned items from the Winter '27 notes as "not quite ready", including Flow Tags and redesigned element search, so do not plan around those yet.
How Has Flow Builder Changed Since the New Flow Wizard?
Creating a flow now starts with a choice, and maintaining one is far easier. The New Flow dialog asks whether you start from scratch or from a template, then lets you search and filter flow types. Since then Salesforce has added saving your own templates, version comparison, collapsible branches, a side-panel debugger and, in Winter '27, Edit History.

Creating flows
- Start from scratch or a template. The choice above arrived in 2023. Spring '25 brought a new Create New Flow experience to the Automation Lightning App with search and filters, and Summer '25 added the same modal in Setup, with categories and your most-used flow types and templates.
- Save as Template. Since Summer '25, the save menu can store a flow as a template, so a team can standardise how common automations start.
- Choose the right type. The type list now runs well beyond screen, autolaunched and record-triggered flows. It includes platform event-triggered, schedule-triggered and orchestration types, among others.

Maintaining flows
- Status at a glance. Flow Builder shows the version number, when it was last modified and whether it is Active or Inactive, so you know which version you are editing before you change it.
- Version comparison. Introduced in Winter '26 for comparing properties, elements, resources and connectors between versions, extended to screen flows in Spring '26, and shown visually on the canvas in Summer '26. A comparison can be shared by URL, which helps code review.
- A tidier canvas. Spring '26 lets you collapse Decision, Loop, Wait and other branching elements. Summer '26 collapses fault paths. Winter '27 adds element groups and the Unused Resources filter.
- One place to manage automation. The Automation Lightning App now monitors flow interviews and resumes paused ones (Spring '25), shows two-way flow dependencies on a Usage tab and run metrics on a Flow Logs tab (Spring '26). The Flow Logs tab relies on Data 360.

If you inherit an org with many flows on the same object, these tools make it practical to consolidate them. Our guides to the Flow Trigger Explorer and a one-flow-per-object strategy explain how to decide what runs, and in what order.
What Can Salesforce Screen Flows Do Now That They Could Not Before?
A screen flow can now fetch data, calculate and update itself without moving to the next screen. Three features make that possible: the Action Button, the Repeater and reactive screen actions. Together they let one screen do work that used to need three screens or a custom Lightning web component, which means shorter flows and fewer clicks for users.
Action Button
GA since Winter '25Best for: lookups and calculations a user triggers on purpose, such as "check availability" or "fetch the account's open cases".
The Action Button runs an autolaunched flow from a screen and makes its outputs available to other components on the same screen. It was beta in Summer '24 and became generally available in Winter '25, which added a running indicator, refreshed inputs and outputs, an In Progress output and a way to disable the button with a Boolean resource. It runs in Lightning runtime, not Classic, and is available from Essentials through Developer editions.
Typical uses: show a table or picklist of records related to the user's selection, pull product data from another system for the user to pick from, build dependent choices, or summarise the user's selections, such as a total amount or an earliest date. Build the autolaunched flow first, then the screen flow that calls it, then the components that use its output.

Repeater
GA since Summer '24Best for: entering several similar records on one screen, such as household members, line items or attendees.
The Repeater holds a set of components that users can add again and again. General availability in Summer '24 allowed custom and standard components inside it, references between its child components, conditional visibility, input validation, help text and debug details. Winter '25 added prefilling it with an existing record collection, so users can edit several records at once. Add the Repeater to a Screen element, place the child components inside it, and map its output collection to a Create or Update Records element. Like the Action Button, it is not supported in Classic runtime.

Reactive screen actions
GA since Summer '25Best for: screens that should respond as the user types or selects, without a button.
Screen actions run an action automatically when a value on the screen changes. Salesforce introduced them in Spring '25 and made automatically triggered screen actions generally available in Summer '25, with run conditions that limit when they fire. Use them for live validation, recalculated totals and lookups that follow the user's input. Keep them light and use run conditions, so an action does not fire on every change and slow the screen down.
Other screen flow additions since 2025
| Release | What was added |
|---|---|
| Spring '25 | Real-time input validation (flow API version 63.0 or later) and a built-in progress indicator with stages |
| Summer '25 | 12-column layout per component, screen-size preview, Visual Picker component, icons in Choice Lookup |
| Winter '26 | Data Table shows Apex-defined types; Display Text gets heading styles, images and alt text; preview with your Lightning or Experience Cloud branding |
| Spring '26 | Message and File Preview components, Kanban Board (beta), component-level styling, and opening a screen flow by URL with input variables |
| Summer '26 | Toast messages, opening a page between screens, Radio Button Group, wider styling overrides including the Action Button |
| Winter '27 | Screen flows as mass quick actions from list views and related lists; Time component |
For a worked example of dependent choices in a screen, see our guide to dependent picklists in screen flows.
Should You Move Approvals and Multi-Step Processes Into Flow?
For new work, yes. Flow Approval Processes are built on the same engine as Flow Orchestration and are the approval tool Salesforce is investing in; its Admins blog calls them the replacement for classic approvals. Flow Orchestration, which coordinates multi-step, multi-person processes, stopped being a paid add-on in February 2026. Classic approvals still work, so migrate them on your own schedule.
Flow Approval Processes, release by release
- Spring '25: approval processes built as autolaunched or record-triggered flows, with steps assigned to queues or public groups, custom notification emails, and approving or rejecting by replying to an email.
- Summer '25: a recall path, delegation using your org's existing delegated approver settings, and submitting a record for approval from another flow.
- Winter '26: debug mode for approvals and orchestrations, and an Approval Designer permission that lets business users design approval processes without full Manage Flow access. Activation still needs Manage Flow or a review.
- Spring '26 and Summer '26: a Request Approval component for record pages, targeted debugging, and unanimous approval for group steps.
- Winter '27: up to 10 approval processes offered from one record page, suspending and resuming submissions, private work items, and deleting approval submissions for GDPR requests.
Flow Orchestration is now standard. From the week of February 16, 2026, orchestration runs are included with no usage-based limits in Enterprise, Performance, Unlimited, Einstein 1 and Developer editions, subject to normal Flow limits. Use it when a process has stages, several people or teams, and background steps between them, such as onboarding a client or approving a contract.
Watch the edition and the contract. Salesforce's announcement says orchestration is subject to edition limits for Flow and suggests discussing contract details with your account executive. Professional and Essentials editions are not in the standard-feature list, so confirm before you design around it.
Our earlier guide to Flow Orchestrator explains stages, steps and work items in more depth; read it alongside the February 2026 Salesforce Admins announcement, which changes the cost side of that decision.
Can AI Build Salesforce Flows for You Yet?
It can draft them, but you still need to design, review and test them. AI flow building has moved back and forth: Einstein for Flow became generally available in Spring '25, Agentforce for Flow was generally available in Spring '26, then Salesforce returned it to beta in Summer '26 because it did not consistently deliver the accuracy complex workflows need. Winter '27 adds Flow Author, also in beta.
| Capability | Release and status | What it does |
|---|---|---|
| Einstein for Flow | Beta Winter '25; GA Spring '25 | Drafted flows and flow summaries from natural language, plus generative formulas |
| Agentforce for Flow | GA Spring '26; Beta again from Summer '26 | Drafts and changes flows from instructions in the Agentforce panel |
| AI troubleshooting | Beta Summer '26 | Explains and suggests fixes for flow errors; needs Data 360, Agentforce and Einstein generative AI |
| Flow Author | Beta Winter '27 | Confirms your intent, then generates a deployable autolaunched, record-triggered, schedule-triggered or screen flow |
| Run Agent element | Summer '25; extended Summer '26 | A flow calls an Agentforce agent, and since Summer '26 can create and configure one from Flow Builder |
The traffic also runs the other way: flows are one of the main ways Agentforce agents do work. You do not assign a flow to an agent directly. In Agentforce Builder you create an agent action that references the flow, as Salesforce's Trailhead module on flows as agent actions shows. Winter '27 also shows agent action details on the Flow Builder canvas. That makes well-named, well-described, single-purpose flows more valuable than ever, because an agent can only be as reliable as the actions it calls.
Our view: use AI to produce a first draft, a summary of an inherited flow, or a formula, then treat the result like a pull request. Check entry conditions, run context, fault paths and bulk behaviour before activation. For agent-driven automation, our Agentforce automation services and AI in Salesforce pages explain how we scope it.
How Do the New Testing and Error-Handling Features Reduce Flow Failures?
They move failures from production to design time. Flow tests can now run from the command line, be tied to flow versions and, with Winter '27's Test Mode beta, be saved from debug runs with assertions. Save-time warnings catch missing required fields, record-lock errors retry automatically, and logs and performance data show what ran. Fault paths are still your job.
| Release | Testing, debugging and resilience |
|---|---|
| Summer '24 | No per-org limit on paused and waiting flow interviews (Enterprise, Performance, Unlimited, Developer); storage can still limit them |
| Summer '25 | Redesigned debug panel; run flow tests from the Salesforce CLI with sf flow run test; flow logging to Data Cloud (uses credits) |
| Winter '26 | Resizable debug side panel with View on Canvas; screen flows use the same debugger as other types |
| Spring '26 | Debug settings kept between saves; flow tests assigned to specific versions |
| Summer '26 | Redesigned validation panel; screen flow test path highlighted on the canvas |
| Winter '27 | Flow Test Mode (beta) with reusable test scenarios and assertions; mock outputs for actions and subflows (beta); retry on record locks; save-time warnings |
Flow Test Mode replaces the Debug button with a Test view and saves a debug run as a manual test scenario you can rerun. It is switched on in Setup under Process Automation Settings, and the beta covers record-triggered and autolaunched flows. Salesforce's announcement of Flow Test Mode notes Flow now runs over 690 billion times a month, which is why testing has become a priority.
Limits that still apply
Removing the paused-interview cap did not remove Flow's other limits. Salesforce's flow limits page lists, among others, 50 versions per flow, up to 2,000 active flows per flow type in Enterprise, Unlimited, Performance and Developer editions (5 in Essentials and Professional), and a 24-hour cap on schedule-triggered flow interviews of 250,000 or 200 per user licence, whichever is greater. Our guide to Salesforce Flow limits and our post on fault path strategies cover how to design around them.
What Happens to Workflow Rules and Process Builder Now?
They still run, but Salesforce no longer supports them. Support ended on December 31, 2025. Active workflow rules and processes keep running and can still be edited, activated and deactivated, but Salesforce provides no bug fixes or customer support for them. Flow is where Salesforce now builds declarative automation, so every legacy rule left running is unsupported risk.
Salesforce's end-of-support article and the Migrate to Flow considerations list the details. Our post on moving beyond Process Builder covers the reasons for the change.
How Should Growing and Mid-Market Companies Adopt New Flow Features?
Adopt features in order of risk removed, not novelty. First retire unsupported automation, then put guardrails around the flows you already run, then simplify user-facing screens, and only then pilot beta and AI features. Do each step in a sandbox during the release preview window, when your sandbox gets the new release weeks before production.
Most of the flow work we see is not about missing features. It is about automation that grew one rule at a time until nobody could say what fires when a record is saved. In one published engagement, from manual entry to real-time Salesforce automation, we replaced manual re-keying of form submissions with Salesforce Flow automations that create Leads, Contacts and Cases, route them to the right owner and send confirmations, with custom Apex for duplicate matching. The case study reports zero manual data-entry steps left in that workflow after go-live.
If you are not sure what your org is running, a Salesforce health check reviews automation, limits and customisations before you change anything. For build capacity, our Salesforce developers work on Flow, Apex and Lightning web components together.
The Bottom Line
The new Salesforce Flow features of 2024 to 2026 make Flow the single place for automation, approvals, orchestration and agent actions, and Winter '27 makes that automation easier to audit, secure and test. Twopir Consulting helps growing and mid-market companies get there: we implement, rescue, optimize, and integrate complex CRM and revenue systems, including the flows that hold them together.
- 1
Migrate every active Workflow Rule and Process Builder process to Flow, and test the result.
- 2
Use Edit History, version comparison and fault paths so every flow change can be traced and recovered.
- 3
Rebuild multi-screen flows with Action Buttons, the Repeater and reactive screen actions.
- 4
Move approvals and multi-step processes into Flow once your edition is confirmed.
- 5
Pilot AI drafting, Flow Author and Test Mode in a sandbox, and keep a human reviewer.
Turn Your Flows Into Automation You Can Trust
Tell us what your org runs today, from legacy rules to screen flows and approvals. We will show you what to migrate, what to consolidate and which new Flow features are worth adopting first.
Schedule a Discovery CallFrequently Asked Questions
Winter '27 is the current release. Salesforce announced it as generally available on October 12, 2026, and it ships with API version 68.0. Its Flow changes include Edit History, element groups, a run mode that enforces user permissions, automatic retry on record-lock errors, screen flows from list views, and Flow Test Mode and Flow Author in beta.
Yes. The Action Button was beta in Summer '24 and became generally available in Winter '25. It runs an autolaunched flow from a screen and makes the outputs available to other components on that screen. It works in Lightning runtime, not Classic, and is available from Essentials through Developer editions.
They still run, but Salesforce ended support on December 31, 2025. Existing rules and processes can be edited, activated and deactivated, but Salesforce no longer fixes bugs in them or provides support. Salesforce recommends Flow for all new automation and the Migrate to Flow tool for converting existing rules and record-triggered processes.
No per-org limit. Summer '24 removed the usage-based limit on paused and waiting flow interviews in Enterprise, Performance, Unlimited and Developer editions. The number can still be limited by your org's available storage, and other Flow limits, such as the daily cap on schedule-triggered interviews, still apply.
No. From the week of February 16, 2026, Flow Orchestration became a standard feature, with orchestration runs included and no usage-based limits in Enterprise, Performance, Unlimited, Einstein 1 and Developer editions. Normal Flow edition limits still apply, and Salesforce suggests confirming contract details with your account executive.
It can draft and change them, but the feature is in beta. Agentforce for Flow was generally available in Spring '26 and returned to beta in Summer '26 because it did not consistently deliver the accuracy complex workflows need. Winter '27 adds Flow Author, also beta. Review and test every AI-drafted flow before activating it.
Flow Approval Processes. They arrived in Spring '25, are built on the Flow Orchestration engine, and have gained recall paths, delegation, group approvals, a Request Approval component and debugging in later releases. Salesforce's Admins blog describes them as the replacement for classic approvals, which still run today.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Salesforce Flow automation, approvals and Agentforce actions, for 500+ clients over 12+ years.