Salesforce Flow Summer ’26: Every Developers should know

If you’ve been tracking Salesforce Flow Summer 26 release notes, you know most releases bring a handful of incremental improvements. The Salesforce Flow Summer 2026 release is different. This one brings AI agents directly into Flow Builder, removes the run entitlement cap on Flow Orchestration, adds date operators that eliminate entire categories of formula workarounds, and overhauls the Screen Flow UX — all in a single release.

This guide covers every significant Salesforce Flow Summer 26 change, organized so you can jump straight to what matters for your role. Whether you’re an admin automating business processes, a developer building complex integrations, or an architect designing enterprise-scale automation, there’s something here that will change how you work.

Production rollout dates: Sandbox preview started May 9, 2026. Production orgs begin upgrading June 5, 2026, with the final wave completing June 12, 2026.

---

Table of Contents

1. What’s New in Salesforce Flow Summer 26? The Big Picture
2. Flow Orchestration — Unlimited Runs, No Entitlement Caps
3. New Date Operators — Goodbye Formula Workarounds
4. Salesforce Flow Summer 26 Fixes Email Template Deployment Bug
5. Unanimous Approvals in Flow Approval Processes
6. Custom Batch Sizes for Scheduled Flows
7. Screen Flow Improvements – Radio Groups, Lookup Names, Styling
8. Collapsible Fault Paths and Element Error Rate Monitoring
9. Natural Language Editing Now Extended to Screen Flows
10. Data Table Lookup Columns Now Show Record Names (Not IDs) with Clickable Links
11. Native Show Toast Action — No More Custom Components for a Simple Notification
12. FAQ

---

What’s New in Salesforce Flow Summer 26? The Big Picture

Three themes define the Salesforce Flow Summer 26 release: AI integration, friction removal, and scalability at enterprise scale.

Salesforce is embedding Agentforce directly into Flow Builder — both as a tool for creating agents and as a debugging assistant. They’re also clearing long-standing bottlenecks: orchestration limits are gone, batch sizes are configurable, and a persistent email template bug that’s been breaking deployments for years finally has a fix.

Here’s a quick summary of every major change and who it affects

---

1. Flow Orchestration — Unlimited Runs, No Entitlement Caps

What This Means for Enterprise Automation

Flow Orchestration run entitlements are being removed entirely in Salesforce Flow Summer 26. If you’ve been holding back on Orchestration-based workflows because of limits, that barrier is gone.

Previously, Flow Orchestration runs counted against a per-org entitlement. For orgs running high-volume orchestrations — think multi-step approval workflows, complex employee onboarding, or coordinated cross-object processes — this cap created real planning constraints. Architects had to decide whether a process was “worth” using Orchestration or whether a simpler (but less capable) approach was safer from a limit standpoint.

Which Editions Are Covered

Flow Orchestration with no run entitlement cap is available in Enterprise, Unlimited, and Einstein 1 editions. Professional edition orgs retain their existing entitlement model — check your contract if you’re on Professional.

Use Cases That Are Now Unlocked

• High-volume order management — coordinating multiple approval stages across large catalogs
• HR onboarding at scale — parallel provisioning steps across systems without worrying about hitting daily limits
• Field service coordination — real-time multi-step workflows triggered by IoT or status changes
• Financial approvals — multi-tier approval orchestrations across business units

If you previously archived an Orchestration design because the limits made it impractical, now’s the time to revisit it.

Read about official Flow Orchestration announcement.

2. New Date Operators — Goodbye Formula Workarounds

This is one of the most practically useful updates in the release. Flow Decision elements now natively supports operators such as Is Today, Is Anniversary of Today, and Last Number of Days.

This means you no longer need to really on writing complete formula resources in the formula and use it in different places. This reduces the complexity and error during development.

Read this official Salesforce Documentation for the complete date operator list.

Which Flow Types Support These Summer 26 Date Operators

These operators work in Record-Triggered Flows, Scheduled Flows, Screen Flows, and Autolaunched Flows. They’re available across all Salesforce editions that support Flow. The operators work on Date and DateTime field types.

Real-World Examples and Use Cases

Renewal reminders: Build a scheduled flow that checks Contract_End_Date__c with the Next Number of Days operator set to 30 — no formula field required.

Birthday/anniversary logic: Use Is Anniversary of Today on a Date_of_Birth__c field to trigger a personalized message, without converting the field to text and comparing month/day strings.

Overdue task escalation: Chain Last Number of Days with a count check — “If Task Due Date was in the Last 7 Days and Status is not Closed, escalate.” Clean, readable, no Apex.

Before this update, every one of these patterns required a formula field, a custom label for today’s date, or a scheduled Apex job. Now they’re three clicks in a Decision element.

---

3. Salesforce Flow Summer 26 Fixes Email Template Deployment Bug

What Was Breaking Before

This bug has frustrated admins and DevOps teams for a long time. When you used a Send Email action in a flow and referenced an email template, the template was stored by its record ID. Since IDs differ between sandboxes and production orgs, deploying the flow via change set or Metadata API resulted in a broken template reference — the flow would either error or send a blank email.

The workaround was manual: after every deployment, someone had to open the flow in the destination org, re-select the template, and re-save. At scale, across multiple flows and multiple environments, this was a real operational tax.

How the Fix Works

Salesforce has changed how the Send Email action stores template references — from a volatile record ID to a durable, cross-org reference tied to the template’s unique name/developer name. This reference survives deployment because it’s resolved in the destination org at runtime, not hardcoded at design time.

You don’t need to change anything in how you build flows. The fix applies automatically to flows that use the Send Email action going forward. If you have existing flows using the old ID-based reference, re-selecting the template and saving the flow once will migrate the reference to the new format.

What Admins and DevOps Teams Need to Do

• Re-save any flows that use Send Email with template references before your next deployment — this migrates existing references to the new format
• Update your deployment runbooks to remove the “manually fix email templates” step
• If you use CI/CD pipelines, verify that flows deploy cleanly end-to-end without the manual correction step

---

4. Unanimous Approvals in Flow Approval Processes

What Changed in Group Approval Logic

Flow Approval Processes now support a “Require unanimous approval” option for group-based approvals. Previously, a group approval step was complete as soon as any group member approved. This works fine for simple “anyone can approve” scenarios, but it broke down for governance processes where all designated approvers must sign off — legal review, security sign-off, executive committees, and so on.

With Summer ’26, you can now specify that every member of the approval group must approve before the record advances.

How to Configure ‘Require Unanimous Approval’

1. Open your Flow in Flow Builder and locate the Approval element
2. In the Approval element configuration panel, select Group as the approver type
3. Choose the relevant queue or public group
4. Check the Require unanimous approval from all group members option
5. Save and activate the flow

The element will now wait until every group member has responded before evaluating the approval outcome. If any member rejects, the rejection logic fires immediately (you can configure this behavior).

Slack Approvals — Acting on Approvals Without Leaving Slack

Summer ’26 also expands Slack integration for Flow Approvals: approvers can now approve, reject, or comment directly from a Slack message, without navigating to Salesforce. The approval card in Slack shows record details, any required context fields, and action buttons. Decisions sync back to the flow in real time.

This is significant for adoption — approval loops often stall because approvers are in Slack but their queue is in Salesforce. Closing that gap directly reduces cycle time.

Limitations to Be Aware Of

• Unanimous approval requires all group members to have active Salesforce licenses
• If a group member is inactive or deleted, the approval step will need manual intervention — build a fault path to handle this
• Slack approval integration requires the Salesforce for Slack app to be installed and users to have connected their accounts

Read this official Salesforce documentation on Flow Approval Process release.

---

5. Salesforce Flow Summer 26: Custom Batch Sizes for Scheduled Flows

Why the Default Batch of 200 Was a Problem

Scheduled Flows process records in batches. The default batch size has always been 200 — the same as Apex trigger batches. For many use cases, that’s fine. But for flows that call external APIs, perform complex calculations, or chain multiple DML operations, a batch of 200 often blows through governor limits or hammers external rate limits.

The only workarounds before Summer ’26 were to reduce the scope of the scheduled flow (filter to fewer records), move the logic to Apex (defeating the point of a no-code flow), or introduce delays and re-runs. None of these were satisfying.

How to Configure Batch Size (1–200) from the Start Element

The batch size setting is now exposed directly on the Start element of a Scheduled Flow:

1. Click the Start element in a Scheduled Flow
2. In the Start element panel, find the Batch Size field under “Run Settings”
3. Enter a number between 1 and 200
4. Save and activate the flow

That’s it. No Apex, no custom metadata, no workaround — the platform handles the rest.

When to Use Smaller Batches

Governor limits: If your flow makes callouts, each callout counts toward the per-transaction limit. A batch of 200 records, each triggering an HTTP callout, will immediately hit the 100-callout limit per transaction. Drop the batch to 50 or 25 to stay within bounds.

External API rate limits: Many third-party APIs (Slack, DocuSign, Stripe, etc.) have per-minute or per-hour rate limits. Processing 200 records simultaneously can saturate these limits and cause failures mid-batch. Smaller batches spread the load.

Complex logic chains: If your flow has 10+ elements per record and involves subflows, the heap size and CPU time per transaction can spike. Smaller batches reduce the per-transaction cost.

Example Scenario

You’re running a nightly scheduled flow that syncs Salesforce Opportunity data to an external ERP via REST API. The ERP limits you to 50 requests per minute. Setting your batch size to 45 gives you a comfortable buffer under the rate limit without needing to redesign the integration.

Read this official Salesforce Documentation on using Custom batch sizes on Flow.

---

6. Screen Flow Improvements – Radio Groups

Screen Flows now include a native Radio Button Group component. Previously, you had to either use the standard Radio Buttons component (limited styling options) or build a custom LWC to get a proper radio button group with the visual design you wanted.

The new component supports horizontal and vertical layouts, custom labels, required field validation, and the same responsive behavior as other native Screen Flow components.

Read this salesforce documentation about Radio button group in Screen Flow.

---

7. Collapsible Fault Paths and Element Error Rate Monitoring

Spring ’26 introduced the ability to collapse individual flow elements on the canvas. Summer ’26 extends this to fault paths — the error-handling branches that extend from elements and often clutter the canvas in complex flows.

How to Collapse and Expand Fault Paths on the Canvas

Click the collapse icon (chevron) on any fault path connector. The fault path elements fold into a compact indicator that shows “N elements” without taking up canvas space. Click the indicator to expand the path back out. Collapsed state is saved with the flow, so collaborators opening the flow see the same canvas state you left it in.

This is particularly helpful for flows with elaborate error handling — retry logic, notification chains, rollback steps — that you don’t need visible while working on the happy path.

Element Error Rate Monitoring — What It Shows and How to Use It

Summer ’26 adds per-element error rate data directly in Flow Builder. When you open a flow, elements that have been generating errors in recent executions are highlighted with an error rate indicator. Click the indicator to see:

• Error frequency (as a percentage of total executions passing through that element)
• Error type breakdown (most common fault codes)
• A timestamp of the most recent error

This replaces the previous workflow of: navigate to Setup → Flow > Pause/Error Log → filter by flow name → try to match error timestamps to specific elements. Now the canvas itself tells you where the problems are.

Read this official Salesforce Documentation to collapse fault path.

---

8. Natural Language Editing Now Extended to Screen Flows

This is the expansion that Screen Flow builders have been waiting for. In Spring ’26, Salesforce introduced the ability to modify flows using plain-English prompts inside the Agentforce panel — but it only worked for record-triggered, scheduled, and a handful of other flow types. Screen Flows were left out.

In Summer ’26, that gap is closed. You can now use generative AI to modify your existing Screen Flows by describing changes in natural language inside the Agentforce panel — adding, removing, or changing screen and action elements without manually adjusting logic in Flow Builder.

In practice, this means you can type something like “Add a screen that asks the user to confirm their shipping address before submitting” and Agentforce will propose the change directly on the canvas. You review it, approve it, and move on. No dragging elements, no rewiring variables, no hunting for the right component in the palette.

The ability to update Screen Flows with natural language was previously restricted to other flow types, making this a long-awaited expansion for anyone building user-facing automation.

How to enable it:

1. Provision and enable Data 360 in your org
2. Turn on Einstein Generative AI in Setup
3. Open any Screen Flow in Flow Builder
4. Click the Einstein/Agentforce panel icon in the toolbar
5. Click Migrate to Agentforce if prompted
6. Type your change request in plain English and review the proposed canvas modifications

What this means for admins and developers

For admins managing complex Screen Flows built over multiple releases, this removes one of the riskiest parts of flow maintenance — manually threading new logic into an existing canvas without breaking what’s already there. You describe the outcome, Agentforce handles the wiring, and you review before committing.

This feature applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions, and is available in all API versions.

Read this official salesforce documentation here.

9. Data Table Lookup Columns Now Show Record Names (Not IDs) with Clickable Links

If you’ve ever built a Screen Flow with a Data Table that included a lookup field, you already know the pain. The component would dutifully display the related record’s ID — a meaningless 18-character string that means nothing to the end user. The fix was always a workaround: create a formula field on the object to build a hyperlink, add that formula column to your table, and hope it didn’t break across orgs.

Summer ’26 reintroduces some much-needed enhancements to how the Data Table component handles lookup fields — and this time they’ve stuck. Instead of having to hack together your own URL visibility solution, you can simply mark a checkbox to display the record name and redirect the user to it when it’s clicked.

You can also configure the field to render as a clickable link that navigates directly to the related record — a clean, professional UX improvement that previously required custom components or Apex.

How to configure it:

1. Open your Screen Flow and select the Data Table component
2. In the column configuration, select the lookup field you want to display
3. Check Show record name to replace the raw ID with the related record’s name
4. Check Enable hyperlink to make the name a clickable link that opens the record in a new browser tab
5. Save and activate

That’s the entire setup. No formula fields, no custom LWC, no Apex.

Why this matters more than it sounds

Linking to related records from Screen Flow Data Tables may be one of the biggest Flow enhancements Salesforce has made in years. It’s the kind of change that looks minor on a release notes page but completely transforms what you can build natively. Think case management views showing the related account name, order tables linking to products, or service screens letting agents click through to related contacts — all without a single line of code or a custom component.

Data table columns tied to lookup fields can now show a human-readable record name at runtime instead of a raw Salesforce ID, with the option to configure that name as a hyperlink that opens the related record in a new browser tab. No more workarounds to surface clickable record names in a data table.

💡 Heads up for Experience Cloud builders: This improvement is especially impactful for customer-facing portals where showing a raw Salesforce ID is not just unhelpful — it looks broken. Native names and links mean your Screen Flow-based portal pages now behave like real applications.

Read the official announcement here.

10. Native Show Toast Action — No More Custom Components for a Simple Notification

Toast messages — those small pop-up banners that confirm a save, warn about missing data, or flag an error — have always been oddly hard to do in Screen Flow. There was no standard action for it. Your options were to install a community package like the popular UnofficialSF Show Toast action, build your own LWC component, or simply go without and leave users staring at a blank transition between screens with no feedback at all.

Summer ’26 finally solves this. You no longer need custom actions just to show a simple toast message. The new native Show Toast action lets you choose the toast style — Success, Information, Warning, or Error — and control whether the message closes automatically or requires manual dismissal. You also define the title and message text users see.

How to configure it:

1. In your Screen Flow, click + Add Element and select Action
2. Search for Show Toast in the action picker — it appears under Standard Actions
3. Set the Toast Style: Success, Information, Warning, or Error
4. Enter a Title and Message (both support flow variables, so you can make them dynamic)
5. Set Dismissal Behavior: auto-close after a duration, or require the user to manually close it
6. Connect it anywhere in your flow logic — after a successful record save, on a fault path, mid-flow as a progress marker

What you can now do natively — without any custom code:

• Confirm a record was created successfully with a green Success toast
• Warn users mid-flow that a related record is missing, without stopping the flow on a separate screen
• Surface a red Error toast on a fault path so users know something went wrong without redirecting them out of the flow
• Display a neutral Information toast as a checkpoint in long multi-step flows

Why this matters for how you build flows

Before this, the cleanest way to show feedback in a Screen Flow was to add a dedicated screen component — a display text element styled to look like an alert — which forced an extra “Next” click from the user. Toast messages are non-blocking: they appear over the current screen, deliver the message, then disappear. That’s a fundamentally better UX pattern for confirmations and lightweight warnings.

The new action lets you control whether the message closes automatically or requires manual dismissal, and lets you define both the title and the message that users see — so you have enough flexibility to cover both quick confirmations and errors that need the user’s attention before they continue.

⚠️ Important: Like all Screen Flow local actions, Show Toast only works when the flow is running in a Lightning Experience page — on a record page, app page, or home page. It won’t fire in the Flow Builder debugger or in Classic. Test it on a record page after activating, not from the debug panel.

Read this Salesforce Documentation to Show Toast Message Action in Flow

---

Frequently Asked Questions About Salesforce Flow Summer 26

What are the most impactful Salesforce Flow changes in Summer ’26?

The three biggest changes are: Agentforce agent creation directly in Flow Builder (AI integration), the removal of Flow Orchestration run entitlement caps (scalability), and the 20 new date operators in Decision elements (friction removal). Any one of these would make a typical release notable — having all three in Summer ’26 makes it an unusually significant update.

Is Flow Orchestration now free for all orgs?

Not for all orgs. The unlimited run entitlement applies to Enterprise, Unlimited, and Einstein 1 editions. Professional edition orgs retain their existing entitlement structure. Check your edition and your contract if you’re not sure which category you fall into.

Do I need to do anything for the email template deployment fix?

For new flows you build after Summer ’26, the fix is automatic. For existing flows that already reference email templates by ID, you need to open each flow, re-select the template in the Send Email action, and save — this migrates the reference to the new durable format. It’s a one-time migration step per affected flow.

Can I use Agentforce inside Flow Builder without extra licensing?

Creating Agentforce agents inside Flow Builder requires an Agentforce license. The Ask Agentforce troubleshooting feature (Beta) is tied to Einstein for Flow, which has its own enablement requirements. Check your org’s licensing in Setup > Company Information > Permission Set Licenses to see what’s available.

When will Summer ’26 be in my production org?

Production upgrades roll out between June 5 and June 12, 2026. Your specific date depends on your Salesforce instance. Look up your instance at trust.salesforce.com to find the exact scheduled window. Sandbox preview environments have been available since May 9, 2026.

What is the new batch size range for Scheduled Flows?

You can now configure batch sizes between 1 and 200 for Scheduled Flows. The setting is on the Start element. The default remains 200 if you don’t configure a custom value, so existing Scheduled Flows won’t change behavior unless you explicitly set a smaller batch.

Does the Screen Flow natural language modification feature require any special setup?

The expanded natural language modification feature for Screen Flows is available in Flow Builder without additional setup, as long as Einstein for Flow is enabled in your org. Navigate to Setup > Einstein > Einstein for Flow to confirm it’s turned on.