Ten Flow improvements landing in Summer '26 — most are quality-of-life polish, two are early AI bets, and one column finally tells you which Flows are quietly failing.
Every Salesforce release falls into one of two camps. Some are capability releases — they hand you new things to build with, and the upgrade conversation centers on what's now possible. Others are polish releases — they don't expand the surface, they reduce its friction. Same canvas, fewer paper cuts.
Summer '26 is the polish kind. The headline 10 features are mostly small ergonomic wins: collapsible fault paths, a redesigned validation panel, native date operators that finally know what "today" means. Not the stuff of keynote demos. The stuff of "oh, that's been bugging me for two years."
Underneath the polish there's something more interesting going on. Agentforce starts threading into Flow Builder for the first time — both as embeddable agents and as a natural-language editing assistant. Both are pilot-only, and that restraint is worth noticing — Salesforce could have shipped this loud. They shipped it cautiously. And one feature almost nobody is leading with — a new column in the Automation app — quietly addresses the longest-standing observability gap in Flow.
Let's walk through what's actually in the box.
Group the ten features by what they actually do for you and the picture clears up fast. Polish is five of the ten — the canvas is louder than it should be, and Summer '26 turns the volume down. Visibility is three — observability has always been Flow's weakest layer, and one quiet column finally moves the needle. AI is two, both pilots.
Read in three buckets, the release tells a story: Salesforce isn't reinventing Flow this season. They're sanding it down and previewing where it's going next.
Five features, all GA, all about reducing friction in the editor itself. None of them change what Flow can do. They change how exhausting it is to look at one for an hour.
The canvas gets the same collapse treatment Decisions and Loops got in Spring '26.
Click a fault path, collapse it, focus on main logic. Particularly useful in flows that share a single error-handling subflow off many elements — those used to spread the canvas wider than your screen for no good reason.
Errors and Warnings reorganize into a card-based list.
The same content, reformatted for scanning. Each issue is a card with the element name, the error text, and a jump-to-element link.
Native operators for "Is Today", "Is Tomorrow", "Is On", and anniversary checks.
The list of new operators is meaty enough to warrant its own table. The big wins are the calendar-relative ones that previously needed a formula or an Apex helper.
| Operator | What it answers |
|---|---|
| Is Today | Does this date equal today's date? |
| Is Tomorrow | Does this date equal tomorrow? |
| Is Yesterday | Does this date equal yesterday? |
| Is On | Does this date equal a literal date you provide? |
| Is This Week / Month / Quarter / Year | Within the current calendar period? |
| Is Last / Next Week / Month / Quarter / Year | Adjacent calendar periods? |
| Is Anniversary Of | Same month and day, any year (birthdays, contract renewals)? |
Caveat worth knowing: these are Date operators, not DateTime. If you're branching on LastModifiedDate or any DateTime field, you'll still need a formula or to extract the Date portion first.
A space-efficient alternative to the standard Radio Buttons screen component.
Visually denser, less vertical real estate, modern styling. Flip the multi-select toggle and it converts to a Checkbox Group.
Lookup field values render as clickable record links instead of bare IDs.
A checkbox on the lookup column unlocks two things: display the record name, and route the user to that record on click. Replaces a half-dozen recipes that involved formula columns and HTML hacks.
Three features that change what you can see. The first one is the most under-covered piece of the release and might be the most consequential one for ops teams.
The Automation app's flow list view gains a column showing the percentage of elements that errored on the most recent run.
Until now, "is this flow quietly failing" required opening the flow, opening a debug log, and digging. Element-level errors caught by fault paths almost never bubbled up to anyone watching the list view. Now they do.
Override the default 200-record batch for Schedule-Triggered Flows.
A simple example: a scheduled flow finds 11 matching records with a batch size of 2. It runs in 6 separate batches instead of one. That spreads the governor pressure and lets you set a ceiling for how much a flow can chew at once.
Custom property editors per input, picklists for action inputs, custom headers on the configuration page.
This is squarely for action developers — package builders, Apex authors, anyone who's ever shipped an invocable action and wished its Flow-side configuration screen could guide the admin instead of presenting a blank textbox. Now you can attach a property editor to a single input, define an input as a true picklist instead of a string, and reorganize the config UI with section headers.
Two features. Both pilot. Both more interesting for what they signal than what they deliver today.
Drop an AI agent into a Flow with custom instructions and actions.
You can either reference an existing Agentforce agent or build a "mini agent" inline — give it instructions, allowed actions, and let the Flow call it. The first GA use case will likely be conversational steps in screen flows: ask the user a question, let the agent route based on the answer.
Ask Agentforce to make changes to a Screen Flow in plain English.
Spring '26 brought NL editing to other flow types. Summer '26 extends it to Screen Flows — historically the hardest variant for AI because layout and interactivity matter as much as logic.
Chris's take, the honest version: This is the door opening, not the door open. The right move this release is to enroll in the pilot if you can, build a throwaway proof-of-concept, and write down what works and what doesn't. The next two releases will tell you whether this is going to change Flow or just decorate it.
A handful of Summer '26 items didn't make the headline ten — either too niche, too preview-only, or too tangentially related to Flow proper. They're worth knowing about anyway.
Different roles, different first moves. Pick one.
When each milestone lands — preview signup, sandbox preview, production rollout weekends.
Spin up a Summer '26 dev org for early testing of GA features.
Salesforce upgrades preview-instance sandboxes. Refresh on a preview-instance sandbox to test against your real metadata.
Standard release-weekend cadence: production orgs upgrade in three waves over consecutive weekends.
Summer '26 won't headline a Dreamforce keynote. The headline 10 are mostly small wins — collapse a path, see the right operator, get a denser radio button. The two AI features are pilots. The most consequential single addition might be a column in a list view.
That's not a complaint. The releases that change a platform aren't always the ones that announce themselves. Watch how often you reach for the new date operators in the next month, how many silent flow failures the new column surfaces in your first sort, how many of your custom actions you rebuild with the new property editors. Those are the real measures.
The interesting question for fall isn't whether AI shows up in Flow — it clearly will. It's whether Global Flow Resources lands as the flagship the preview is hinting at. Until then, take the polish and the visibility. They're free.
Search components, articles, and tags