Every Salesforce release, the Flow section of the release notes is the one worth reading first. Summer ’26 did not disappoint — new date operators, batch size control for scheduled flows, collapsible fault paths, natural language updates for Screen Flows via Agentforce, and a genuinely better radio button experience.
Here is the full breakdown of what landed, what it does, and when you would actually use it.
| Feature | What it does | Who benefits most |
|---|---|---|
| 📅 Date Field Operators | New operators: Is Today, Is Tomorrow, Is On, Anniversary. Applies to Date fields only — not DateTime. | Admins building renewal reminders, SLA tracking, birthday campaigns, or any time-sensitive record logic. Eliminates the need for formula field workarounds. |
| ⚙️ Scheduled Flow Batch Size | Custom batch size control instead of the fixed default of 200. Smaller batches = lower governor limit risk. Larger batches = faster processing. | Any org running Scheduled Flows against unpredictable record volumes. High-value for flows with DML operations or external callouts. |
| 🗂️ Collapsible Fault Paths | Fault paths in Flow Builder can now be collapsed. Canvas continues the visual cleanup started in Spring '26 with collapsible Decisions and Loops. | Admins managing complex flows with shared error-handling subflows. Large production flows become significantly more readable. |
| 🤖 Natural Language Screen Flow Updates | Agentforce natural language editing now supports Screen Flows. Describe a change in plain language, Agentforce makes the adjustment. Early access — review required. | Admins who want to trial Agentforce-assisted flow building. Works well for additive changes with clear descriptions. Complex logic still needs manual work. |
| 🔘 Radio Button Group | New compact visual component replacing standard radio buttons in Screen Flows. Horizontal and vertical layout options, less vertical space per option. | Any admin who has built Screen Flow intake forms and found standard radio buttons too space-heavy. Direct UI improvement for end users. |
| 📧 Email Template Deployment Fix | Send Email Actions using Email Templates now deploy correctly between environments. Fix is in "Show advanced options" in the action properties. | Orgs with proper sandbox-to-production workflows who have been maintaining environment-specific flow versions as a workaround. One-time fix. |
1. New date field operators
Flow now supports four new date operators: Is Today, Is Tomorrow, Is On, and anniversary-based matching for date fields. For any flow that does time-sensitive record logic, this is a meaningful improvement over the workarounds that previously required formula fields or date math.
The practical applications are immediate. A renewal reminder flow that should trigger 30 days before the contract end date can now use Is On with a relative date formula rather than a calculated checkbox field. A birthday-triggered campaign can fire using the anniversary operator without building a custom evaluation layer. Any flow checking whether a date falls within a specific window benefits directly.
One important constraint: these operators apply to Date data types only, not DateTime. If your date field includes a time component, the new operators will not be available. This is worth checking against your object schema before building.
2. Batch size control for Scheduled Flows
Scheduled Flows now support a custom batch size setting. The default has always been 200 records per batch, which is a sensible baseline for most use cases but creates problems when qualifying record counts are unpredictable and the flow logic includes DML operations, callouts, or other governor limit-sensitive steps.
Smaller batch sizes reduce the risk of hitting limits when record volume spikes. A flow that runs cleanly on 200 records can fail when it processes 1,400 and the batch triggers 200 SOQL queries rather than 200. Reducing the batch to 50 adds processing time but removes the failure risk.
The tradeoff runs in both directions. Larger batches complete the full scheduled run faster when record volume is stable and governor limits are not a concern. The new control lets admins tune this explicitly rather than accepting a single default for every scenario.
3. Collapsible Fault Paths
Fault paths can now be collapsed in Flow Builder, following the Spring ’26 changes that added collapsible Decisions and Loops. This is a quality-of-life improvement rather than a capability change — fault paths do not behave differently when collapsed — but for anyone managing complex flows with shared error-handling subflows, the canvas clarity improvement is real.
Large production flows become difficult to read when fault paths branch from every element that can fail and the canvas becomes a sprawl of error-handling logic. Collapsing fault paths lets admins focus on the main execution path during review and debugging, and expand fault handling when needed.
4. Update Screen Flows with natural language via Agentforce
Agentforce-powered natural language editing, which launched for Record-Triggered and Scheduled Flows in Spring ’26, now extends to Screen Flows in Summer ’26. Admins can describe the change they want in plain language — ‘add a required email field before the address step’ — and Agentforce makes the adjustment in Flow Builder.
This feature is in early access and the honest framing is the right one: it works well for additive changes that are clearly described. Reorganising a complex screen, adjusting conditional visibility rules, or changes that require understanding of downstream logic still need manual work. Furthermore, any Agentforce-generated flow update should be reviewed in the canvas before activation, which the current implementation requires regardless.
5. Radio Button Group component
Screen Flows have a new Radio Button Group component — a compact visual replacement for the standard radio button layout that has long been one of the more space-inefficient UI patterns in Salesforce forms.
The new component groups options horizontally or vertically in a tighter layout with cleaner visual weight. For any admin who has built a Screen Flow intake form and winced at how much vertical space three radio button options consume, this is a direct improvement. No configuration change required for existing flows; it is a new component available in the Screen Flow component palette.
6. Email Template deployment fix
Using an Email Template in a Send Email Action no longer breaks when deploying the flow between environments. This has been a persistent pain point for orgs that follow proper sandbox-to-production workflows: a flow using an Email Template could fail deployment because the template reference was environment-specific.
The fix is in the Show advanced options section of the Send Email Action properties. Admins who have been maintaining separate flow versions per environment to work around this can now maintain a single flow and deploy it cleanly.
Six changes, two of which have been on the admin wishlist for multiple releases. The email template deployment fix alone is worth reading the Summer ’26 release notes for if you manage flows across sandbox and production environments.
Building Flows that use date logic and have been waiting for proper date operators? Summer ’26 is your release. Reach out via truesolv.com if you want help reviewing your automation architecture before the upgrade lands. Follow us on LinkedIn for more admin-focused Salesforce content.
