Key takeaways
- Winter ’27 is one of the most significant Flow Builder releases in years, with a redesigned canvas experience.
- Test Mode, in beta, brings debugging and repeatable test scenarios together in one place.
- New Split by Field Value and Split by Date elements, flow tags and unused-element filtering make large flows easier to build and organize.
- Screen flows can run on multiple records from list views and related lists.
Salesforce’s Winter ’27 release arrived in the autumn of 2026, and Flow Builder is the headline. Several long-requested capabilities landed at once, aimed at making large, complex flows easier to build, test and maintain.
Test Mode (beta)
Test Mode brings debugging and repeatable testing into a single interface. Builders can save a setup as a scenario and rerun it after making changes, which makes regression testing of declarative automation much more practical. As a beta feature, use it alongside existing flow tests and sandbox testing.
Building and organizing large flows
- Split by Field Value and Split by Date elements offer new ways to branch logic, reducing nested decisions.
- Flow Tags help organize and find flows across an org.
- Filter by unused elements and resources highlights leftovers that can be removed.
- Element grouping lets builders group related elements on the canvas.
- Edit History shows changes made within a flow.
Salesforce noted that some of these, such as element grouping and edit history, roll out gradually, so they may not appear in every org at once.
Screen flows on multiple records
Admins can launch screen flows for multiple records from list views and related lists, enabling guided mass updates and actions without custom components. Test carefully with realistic record counts and consider governor limits.
A refreshed builder
The canvas was redesigned, with elements grouped by type in a side menu, and preferences such as hiding API names or collapsing labels and descriptions to reduce clutter.
What admins should do
- Review Release Updates and retirements for this release in Setup and the release notes.
- Regression test critical flows, integrations and custom components in a preview sandbox.
- Pilot Test Mode on one complex flow and save scenarios for future releases.
- Introduce flow tags and a naming convention to organize existing automation.
- Remove unused elements and resources flagged by the new filter.
Based on release coverage and previews at the time of writing; beta features and gradual rollouts mean availability can vary. Confirm details in the official Winter ’27 release notes.
Our administration and support team reviews each release and helps clients adopt the features that matter.
How to use Test Mode well
- Start with flows that have the most business impact or change most often.
- Save scenarios for the main paths and the tricky edge cases.
- Rerun scenarios after every change and before each release.
- Keep using flow tests in your deployment pipeline where you have them.
Saved scenarios become a lightweight regression suite that grows over time, which is exactly what declarative automation has historically lacked.
Frequently asked questions
Is Flow Test Mode generally available?
It was released as a beta in Winter ’27. Use it alongside established testing practices.
Why do we not see element grouping yet?
Some Winter ’27 Flow features roll out gradually, so they may appear in orgs at different times.
Can screen flows update many records at once now?
Winter ’27 allows launching screen flows on multiple records from list views and related lists; design them with bulk behavior and limits in mind.
