Salesforce Flow Orchestration is Free in Summer 26
Flow Orchestration used to cost extra. Now it does not. Starting with Summer ’26, Flow Orchestration runs are included in Enterprise, Performance, Unlimited, and Developer editions without usage-based limits. If you ruled it out before because of the pricing, that calculation is gone. Here is what Flow Orchestration actually does, and why it is worth a fresh look. What Flow Orchestration actually is A regular Flow handles a trigger and a sequence of automated steps. It runs, completes, and is done — typically in seconds, with no pause for a human to weigh in partway through. Flow Orchestration is built for a different category of process: multi-step, multi-user business processes that require coordination across people, systems, and time. The work needs to pause, wait for a specific person to make a decision, branch based on that decision, and continue — all in a monitored, auditable way, potentially over hours, days, or weeks. The distinction matters because many processes that orgs currently handle through a combination of email, manual task assignment, and someone remembering to follow up are exactly the kind of process Orchestration is built for. The reason most orgs have not built these in Salesforce is that Orchestration previously carried a usage-based cost that made it hard to justify for internal process automation rather than customer-facing workflows. Characteristic Regular Flow Flow Orchestration Duration Runs and completes in seconds. No pause for human input mid-process. Can span hours, days, or weeks — pauses at human steps and resumes when action is taken. Human involvement Limited to triggering the flow or responding to a single approval step bolted on separately. Built-in stages where specific people are assigned tasks, make decisions, and the process branches based on their input. Visibility No persistent status view. Once running, you cannot easily see “where” the flow currently is. Defined stage model — anyone can see which stage a process instance is currently in and who owns it. Multi-department coordination Difficult — typically requires chaining multiple flows and manual handoffs between departments. Native — parallel and sequential stages across different teams with a single coordinated process instance. Best for Record updates, notifications, single-step automations, data validation, immediate actions triggered by a record change. Onboarding processes, approval chains, multi-department workflows — anything where “who does this next and when” is the core challenge. Cost (Summer ’26) Included in all editions, as always. Now free Included in Enterprise, Performance, Unlimited, and Developer editions — no usage-based limits. A simple orchestration, structurally The shape of an orchestration is consistent regardless of the specific process: a system step does something automatically, a human step pauses and waits for a person to act, the orchestration branches based on what that person decided, and the process continues — potentially with more human steps, more branches, and a final system step that records the outcome. A Simple Flow Orchestration — Four Stages Stage 1 System action e.g. create record AUTOMATED Stage 2 Human approval Manager reviews and decides PAUSES & WAITS Stage 3 System action e.g. update fields AUTOMATED Stage 4 Branch → Approved path → Rejected path OUTCOME RECORDED Status, owner, and stage are visible to anyone checking on the process — not just whoever is currently assigned. What makes this different from a Flow with an Approval Process attached is the structure and visibility. Orchestration gives you a defined stage model — each stage has a clear owner, a clear set of possible outcomes, and a status that is visible to anyone checking on the process, not just the person whose turn it currently is. For processes spanning multiple departments, that visibility is often the missing piece. Three workflows worth building now that it is free New employee onboarding across IT, HR, and the hiring manager Onboarding touches multiple departments with sequential and parallel dependencies: IT needs to provision accounts, HR needs to complete paperwork, the hiring manager needs to prepare the first-week schedule, and some of these steps depend on others completing first. An orchestration can sequence IT provisioning after HR confirms the start date, run HR paperwork and manager prep in parallel, and surface a single status view to whoever is coordinating the new hire’s first day. The alternative — the current state at most orgs — is a checklist in a shared document and a series of Slack messages asking whether each step is done yet. Orchestration replaces the asking with visibility. Contract approval chain with parallel legal and finance review A contract above a certain value needs review from legal and finance before it reaches an executive for final sign-off. Legal and finance review can happen in parallel — neither depends on the other — but the executive sign-off step depends on both being complete. Orchestration models this directly: a parallel stage for legal and finance, a convergence point that waits for both to complete, then a sequential executive approval stage. The audit trail shows who reviewed what and when, without anyone needing to track it manually. Deal desk workflow for non-standard pricing approvals Non-standard pricing requests — discounts above a threshold, custom payment terms, non-standard contract clauses — typically need sign-off from sales leadership, finance, and sometimes RevOps, in an order that depends on the specific request. An orchestration can route the request to the right combination of approvers based on the deal characteristics, track where it currently sits, and notify the rep when a decision is made. The business value here is speed: deal desk requests that currently take days because they sit in someone’s inbox move faster when the orchestration actively routes and tracks them, and the rep has visibility into where the holdup is rather than just waiting. 3 Workflows Worth Building Now That Orchestration Is FreeProcesses most orgs currently run on email, shared docs, and hoping someone follows up 👋New employee onboardingIT provisioning, HR paperwork, and hiring manager prep — sequenced and parallelised with a single status view for whoever is coordinating the new hire’s first day.Stages: HR confirms start date
Salesforce Q1 FY27 Earnings
Salesforce reported Q1 FY27 revenue of $11.13 billion on May 27. Non-GAAP EPS came in at $3.88, beating analyst estimates by nearly 24 percent. AI product revenue grew 205 percent year over year. The stock still closed mostly flat and remains down roughly 30 percent year to date. The market is worried about one thing. The numbers tell a more interesting story than the price does. Salesforce Q1 FY27 — Reported May 27, 2026The numbers behind a quarter the market shrugged at $11.13B+13% YoYQ1 FY27 revenue $3.88+50% YoYNon-GAAP EPS — beat estimates by ~24% +205%YoY growthAI product revenue growth 1M+6 weeksSlack MCP active users since launch +400%QoQPublic Sector Agentic Work Units growth $67.9B+11% YoYRemaining Performance Obligations Source: Salesforce Q1 FY27 earnings release, May 27, 2026. Stock closed roughly flat on the day and remains down approximately 30% year to date. The headline numbers Revenue of $11.13 billion represents 13 percent year-over-year growth — a meaningful acceleration for a company of Salesforce’s size. Non-GAAP earnings per share of $3.88 grew 50 percent year over year, well ahead of the operating leverage the revenue growth alone would suggest, indicating margin expansion alongside top-line growth. The number that should anchor the AI conversation is AI product revenue growing 205 percent year over year. This is not a small product line growing off a tiny base in a way that produces an impressive-looking percentage. At Salesforce’s scale, 205 percent growth in a product category represents a substantial absolute dollar contribution and a clear signal of enterprise adoption momentum. Two operational metrics reinforce the adoption story. Slack MCP — the Model Context Protocol integration that exposes Slack to AI agents — surpassed 1 million active users within six weeks of launch. Public Sector Agentic Work Units, the metric Salesforce uses to track actual agent task completion in government deployments, grew nearly 400 percent quarter over quarter. The SaaSpocalypse narrative — and why it is incomplete The bear case on Salesforce and software companies broadly is some version of “AI agents replace software seats, so software companies lose revenue as customers need fewer licenses.” This narrative — sometimes called the SaaSpocalypse — has weighed on software valuations broadly, and Salesforce’s roughly 30 percent year-to-date decline reflects that the market has been pricing this risk into the stock regardless of what the earnings reports show. The Q1 FY27 numbers complicate this narrative directly. More than 50 percent of Agentforce and Data 360 bookings in the quarter came from existing Salesforce customers. These are not new logos replacing a competitor’s seats with Agentforce. These are existing customers adding AI products on top of their current Salesforce footprint. If the SaaSpocalypse thesis were playing out as the bears describe, the expected pattern would be existing customers reducing their core CRM seat counts while shifting spend to AI tools — net negative or flat revenue from the existing base. What Q1 FY27 shows instead is existing customers expanding their total spend by adding AI products alongside their existing licenses. That is an expansion pattern, not a substitution pattern. 🐻 The SaaSpocalypse Narrative 💬AI agents replace software seats. Companies need fewer licenses as agents take over tasks. 💬Existing SaaS revenue is at structural risk as customers consolidate spend toward AI tools instead of per-seat software. 💬A ~30% YTD decline in the stock reflects the market pricing this risk into software valuations broadly. 💬Expected pattern: existing customers reduce core seat counts while shifting spend to AI — net flat or negative revenue from the base. 📊 What Q1 FY27 Actually Shows ✓50%+ of Agentforce and Data 360 bookings came from existing customers — not new logos replacing competitors. ✓Existing customers are adding AI products on top of their current footprint, not substituting for it. ✓RPO grew 11% YoY to $67.9B — contracted future revenue is expanding, not contracting. ✓The observed pattern is expansion, not substitution — existing customers increasing total spend by adding AI alongside core licenses. The FY27 guidance signal Salesforce raised the midpoint of its full-year FY27 guidance to a range of $45.9 billion to $46.2 billion. Guidance increases are a management signal about confidence in forward visibility — companies do not raise full-year guidance one quarter into the year unless the underlying business trends support it. The FY27 guidance range, set against FY26 actual revenue of $41.5 billion, implies continued double-digit growth at a company of Salesforce’s scale. For a business frequently characterised in market commentary as mature and slow-growing, sustained double-digit growth on a $40B+ base is a different growth profile than the narrative suggests. FY27 Guidance vs FY26 Actual Revenue $41.5BFY26 ActualFull year, reported Feb 2026 $45.9B – $46.2BFY27 GuidanceFY27 Guidance (raised)Midpoint implies ~10.6% growth Raising full-year guidance one quarter in is a confidence signal — management does not do this unless underlying trends support it. What this means if you run your business on Salesforce The remaining performance obligations figure — $67.9 billion, up 11 percent year over year — represents contracted future revenue that customers have already committed to. This is not a speculative pipeline number. It is signed commitments. For Salesforce customers evaluating their own platform roadmap, the practical read is straightforward: $67.9 billion in RPO is not the profile of a company that customers are leaving en masse, and the AI product growth — driven primarily by existing customers expanding their footprint — suggests that the platform investment thesis from a customer’s perspective remains intact. This does not mean every Agentforce or Data Cloud investment is automatically worthwhile for every org. It means the platform-level uncertainty that the stock price reflects is not, based on this quarter’s numbers, primarily a story about customers leaving or reducing their commitment to Salesforce as infrastructure. A 30% stock decline and 205% AI revenue growth are both true at the same time. The market is pricing a risk that this quarter’s data does not yet confirm. Whether that risk materialises in future quarters is a different question than whether the Q1 FY27 numbers themselves were good
Salesforce Data 360 MCP Server Is in Developer Preview
On May 26, Salesforce announced that the Data 360 MCP Server is now in Developer Preview. The idea is direct: every piece of data in your Salesforce Data Cloud is now reachable by any AI agent that speaks Model Context Protocol. Your CRM context, unified customer profiles, real-time data streams — accessible from Claude Code, Cursor, or any MCP-compatible agent tool without writing a custom API wrapper. Data 360 MCP Server — How Data Cloud Connects to AI Agents Salesforce Data Cloud • Unified customer profiles • Audience segments • Calculated insights • Data streams • Identity resolution exposes Data 360 MCP Server Developer Preview Trust Layer protected tool calls MCP-compatible AI agents Claude Code Cursor / Codex Agentforce Studio Custom MCP clients Any agent that speaks MCP No custom API wrapper required. Data arrives through the same trust layer as other Agentforce data access. What the Data 360 MCP Server actually exposes The server gives AI agents structured access to Data Cloud data — unified customer profiles, audience segments, data streams, calculated insights, and identity resolution outputs. These are the data objects that previously required SOQL-like queries against the Data Cloud query engine or custom API development to surface. Through the MCP interface, an agent can retrieve a unified customer profile by identity, query segment membership for a specific individual, pull calculated insight values for an account, or read real-time data stream events — using the same tool-call pattern it would use to interact with any other MCP server, without learning a proprietary API. The significance is in the combination. An agent building a renewal recommendation previously had access to Salesforce CRM data — the account record, the opportunity history, the activity log. What it did not have was the Data Cloud layer: the calculated health score from product usage, the segment membership that reflects behavioural patterns, the cross-channel identity resolution that unifies how the same customer appears across touchpoints. The Data 360 MCP Server adds that layer. Why this changes how agents reason The practical difference between an agent with CRM access and an agent with CRM plus Data Cloud access is the difference between structured records and contextualised customer intelligence. An agent reviewing a renewal opportunity can currently see: account name, ACV, contract end date, last activity log, open support tickets. With the Data 360 MCP Server, that same agent can also see: the customer’s health score calculated from product usage patterns, their segment membership indicating they are in a high-churn-risk cohort, and their identity resolution confirming that two separate records in the CRM are the same individual. Because the data arrives through the MCP interface with the same trust layer protections as other Agentforce data access, the agent’s data handling governance applies uniformly — no separate security configuration needed for the Data Cloud layer. What is available in Developer Preview vs. what is coming Capability Available in Developer Preview Expected at GA Unified customer profile retrieval ✓ Query by identity, return full profile with attributes — Audience segment membership ✓ Query segment membership for a specific individual or account — Calculated insights reads ✓ Return health scores, propensity scores per record — Identity resolution queries ✓ Cross-reference unified identity across touchpoints — Data stream reads ✓ Basic event stream data — subject to Data Cloud sync latency Real-time streaming subscriptions Write-back to Data Cloud ✗ Not yet available Agents will be able to update Data Cloud records based on reasoning output Complex data stream subscriptions ✗ Not yet available Subscribe to data stream events as part of agent trigger logic Production org access ✗ Developer Edition orgs with Data Cloud only Full production org access at GA Developer Preview gives access to the core unified profile retrieval, segment queries, and calculated insight reads. The key constraint is data freshness: Data Cloud data surfaces through the MCP Server with the same refresh latency as the underlying Data Cloud sync. For most use cases this is acceptable. For agents reasoning about real-time events, it is worth understanding the lag characteristics of your specific data streams before building workflows that depend on sub-second freshness. Developer Preview access path Data 360 MCP Server — Developer Preview Access Path4 steps 1Confirm your org has Data Cloud enabledDeveloper Edition orgs with Data Cloud access qualify for Developer Preview. If you do not have a Data Cloud-enabled org, spin up a Developer Edition at developer.salesforce.com — the fastest path to experimenting. 2Enable the Data 360 MCP Server in SetupOpen Setup → search for MCP Servers. The Data 360 MCP Server appears in the available server list for Developer Preview-enrolled orgs. Enable it and configure which agents have access to which data objects.Setup → MCP Servers → Data 360 MCP Server → Enable 3Connect an MCP-compatible clientClaude Code, Cursor, Agentforce Studio, or any MCP-compatible development environment can connect once the server is enabled. The server returns a tool manifest — no custom authentication code required beyond the standard MCP handshake. 4Test with a unified profile retrievalPull a known profile by ID, confirm the MCP Server returns the same data as the Data Cloud UI, and verify that segment membership and calculated insights are included in the response. This confirms the data path is working before building agent logic on top of it. Developer Preview is the right time to experiment, not the right time to build production workflows. Map your architecture, test your data access patterns, and identify what works before GA removes the preview caveats. The orgs that move through this now will deploy faster when GA lands. Data 360MCPData CloudSalesforce DevAgentforce Share: LinkedIn Twitter / X Copy link In this article 01What it exposes 02Why it changes agent reasoning 03Preview vs. GA capabilities 04Access path — 4 steps Developer Preview status Unified profilesQuery by identity — live Segment membershipPer individual — live Calculated insightsHealth scores — live Write-backExpected at GA Production orgsDev Edition only now Quick access path 1️⃣Enable Data Cloud in org 2️⃣Setup → MCP Servers → Enable 3️⃣Connect MCP
Salesforce Summer 26 Release Features
Salesforce announced Summer ’26 on May 11 and set the general availability date for June 15. The headline: 17 major capabilities, all pointing in one direction. Agentforce is no longer a feature layer on top of the platform. In Summer ’26 it is becoming the operating layer underneath everything else. Here is what actually landed and what it means for your org. Salesforce Summer ’26 — Five Changes That Shape the Platform 🤝Multi-Agent OrchestrationAgents delegate to specialist agentsOne customer-facing contact point, multiple specialist agents working behind the scenes. Triage → delegate → coordinate — without the customer switching interfaces.GA — Summer ’26 ⚡Agentforce Self-ServiceHelp Agent in 10 clicks or fewerDeploy a Help Agent to your public website, Portal, or WhatsApp in a guided setup — designed for teams who want to trial Agentforce without a multi-week implementation.GA — Summer ’26 🛡️Security MeshUnified security fabric + risk scoringDisconnected security alerts across Service Cloud, Sales Cloud, and Experience Cloud unified into a single fabric with AI-generated risk scores. Agentforce activity included.GA — Summer ’26 🔄Flow Orchestration — FreeIncluded in Enterprise and aboveFlow Orchestration moves from a usage-limited add-on to included in Enterprise, Performance, Unlimited, and Developer editions. No usage caps, no add-on cost.Now included 📊Tableau over Model Context ProtocolAnalytics engine exposed to Agentforce agentsTableau’s analytics engine is now reachable by Agentforce agents over MCP, protected by the Agentforce Trust Layer. Agents can query revenue trends, spend analytics, and historical reports as part of their reasoning — without requiring a human to pull the report first. Closes the gap between CRM data and the BI layer.GA — Summer ’26 Multi-Agent Orchestration For most of Agentforce’s history, an agent was a single system handling a single domain. A service agent answered product questions. A sales agent qualified leads. Each worked independently and each required its own configuration. Multi-Agent Orchestration changes that architecture. Agents can now delegate tasks to specialist agents within the same org. One customer-facing contact point, multiple agents working behind the scenes: a triage agent receives the request, determines which specialist — a billing agent, a technical support agent, a returns agent — should handle it, delegates the task, and coordinates the result back to the customer without the customer ever switching interfaces. The practical implication for orgs with complex service or sales workflows is that you can build specialist agents for distinct domains and let orchestration handle the coordination, rather than trying to build one agent that knows everything. Simpler individual agents, more reliable outcomes at the orchestration level. For developers, the build model changes too. Agent teams can be tested and deployed independently. Failures in one specialist agent are contained rather than cascading through the entire interaction. Agentforce Self-Service The barrier to deploying an Agentforce Help Agent drops significantly in Summer ’26. Agentforce Self-Service is a setup path that gets a Help Agent deployed in 10 clicks or fewer — configured, grounded in your knowledge base, and ready to go on your public website, the new Portal experience, or WhatsApp. The positioning is explicit: Salesforce is targeting the orgs that have heard about Agentforce but found the implementation path too complex for their team size or technical capacity. Self-Service is designed to remove that barrier without removing the ability to customise later. For admins at smaller orgs who have been waiting for a way to trial Agentforce without a multi-week implementation project, this is the most directly actionable Summer ’26 announcement. For larger orgs, the Self-Service path is worth understanding as a rapid prototyping route before committing to a full agent build. Security Mesh Security Mesh unifies data sources across the Salesforce platform into a single security fabric and transforms disconnected access logs and alerts into intelligent risk scores. Instead of reviewing separate security events across Service Cloud, Sales Cloud, and Experience Cloud independently, Security Mesh provides a unified view with AI-generated risk assessment. The practical value for compliance-minded orgs is in audit efficiency. Security events that previously required cross-referencing multiple tools to understand their combined significance are now surfaced as correlated risk signals. Additionally, Security Mesh integrates with the Trust Layer that governs Agentforce agents, meaning agent activity is included in the unified risk picture rather than existing as a separate data source. Flow Orchestration now free Flow Orchestration moves from a usage-limited add-on to an included feature in Enterprise, Performance, Unlimited, and Developer editions without usage-based limits. This removes the licensing conversation from any multi-step process automation project. The timing is intentional. As Agentforce agents become more common in Salesforce orgs, the need to coordinate complex multi-step workflows across agents, humans, and systems increases. Flow Orchestration is the tooling that handles that coordination on the Salesforce side. Making it free removes the last friction point from adopting it broadly. For orgs that evaluated Flow Orchestration and passed because of cost, Summer ’26 is the time to revisit any approval workflows, cross-department handoff processes, or multi-system coordination tasks that are currently running on manual steps or basic Flow. Tableau over Model Context Protocol Tableau’s analytics engine is now exposed to Agentforce agents over the Model Context Protocol, protected by the Agentforce Trust Layer. An agent reasoning about a customer renewal can query Tableau for historical revenue trends. An agent managing a procurement workflow can pull spend analytics directly from the BI layer without requiring a human to run the report first. For data-heavy orgs, this is the most architecturally significant Summer ’26 addition after Multi-Agent Orchestration. It closes the gap between Salesforce CRM data — which agents have had access to — and the analytical layer that lives in Tableau but has been outside the agent’s reach. Role Most relevant Summer ’26 feature What to do now Admin Agentforce Self-Service lowers the barrier to deploying a Help Agent to your website or Portal. Flow Orchestration now free removes the licensing blocker for multi-step approval workflows. Explore Try the Self-Service setup in a sandbox. Identify one approval workflow worth rebuilding in Flow Orchestration now that cost is not a
Salesforce Summer 26 Admin Checklist
The Summer ’26 production upgrade is landing on June 5 and June 12 for most Salesforce orgs. Sandboxes have been on preview since May 8, which means there is no excuse for surprises on production upgrade weekend. Here is the pre-upgrade checklist every admin needs before their org flips. Summer ’26 Production Upgrade Weekends 🚨 June 5 — TomorrowMain production waveMost orgs on NA, EU, and AP instances. If your org is on this wave, the checklist below needs to be complete today — not this weekend. 📅 June 12 — 8 daysFinal production waveRemaining instances. You have until June 11 EOD to complete all mandatory items. Use the time — do not save this checklist for June 10. The mandatory items — these break things if skipped 1. SAML migration New SAML defaults are enforced in Summer ’26. If your org uses SSO via SAML — whether Salesforce is the identity provider, the service provider, or both — you need to verify your Auth Provider configuration and test the full login flow in your Summer ’26 sandbox before production upgrade. A SAML configuration that worked in Spring ’26 may fail after the upgrade if the new defaults require updated settings. Additionally, Triple DES signing for SAML SSO stops working entirely in Summer ’26, as announced in Spring ’26. Any SAML configuration using Triple DES as the signing algorithm breaks on upgrade regardless of whether you took any other action. 2. Apex sharing and security defaults New Apex security behaviors are enforced. Custom Apex code that relies on specific sharing model assumptions from earlier releases needs review. If your org has custom Apex classes managing record-level access or security, test them against the Summer ’26 sandbox before your production upgrade date. 3. Standard Omni-Channel retirement Standard Omni-Channel was retired June 1. If your production org has not migrated to Enhanced Omni-Channel Routing, this is now urgent — not scheduled. Completing the migration before your production upgrade date is the priority. See the dedicated Omni-Channel migration article for the correct four-step sequence — channel migrations must happen before the routing switch is enabled. 4. Legacy PDF generation retirement A legacy PDF rendering behavior is retired in Summer ’26. Any process that generates PDFs from Salesforce — Quote PDFs, Visualforce-generated reports, any custom PDF output — should be tested in the Summer ’26 sandbox to confirm the output is correct before production upgrade. PDF rendering changes are difficult to detect until something generates incorrectly in front of a customer. Summer ’26 Pre-Production Upgrade ChecklistBefore June 5 or June 12 Mandatory — breaks things if skipped SAML auth provider configuration verifiedMandatoryNew SAML defaults enforced. Test full SSO login flow in Summer ’26 sandbox. Triple DES signing algorithm stops working entirely — update to SHA-256 if still using Triple DES.↳ Breaks: SSO login fails for all SAML-authenticated users after upgrade Custom Apex sharing code reviewedMandatoryNew Apex security defaults enforced. Custom Apex classes managing record-level access or sharing rules need testing in sandbox against the new defaults. Run Apex tests in the Summer ’26 sandbox before production upgrade.↳ Breaks: Record access violations or unexpected sharing behaviour in Apex-governed objects Enhanced Omni-Channel migration completeMandatory · UrgentStandard Omni-Channel retired June 1. Migrate service channels (Live Agent, SMS, Messenger) first, then enable Enhanced routing. Test agent login and work item routing in sandbox end-to-end.↳ Breaks: Agents cannot log in to Omni-Channel, work items stop routing entirely PDF generation processes tested in sandboxMandatoryLegacy PDF rendering behaviour retired. Any process generating PDFs from Salesforce — Quote PDFs, Visualforce reports, custom PDF output — must be tested in Summer ’26 sandbox.↳ Breaks: Incorrectly formatted or failed PDF generation for customer-facing documents Recommended — should be done; will not immediately break Agentforce agent configurations reviewedRecommendedSummer ’26 changes agent lifecycle defaults. If your org has agents in production, review the Agentforce Summer ’26 release notes and test agent initialisation, session handling, and error surfacing in sandbox. Evaluate Flow Orchestration for existing processesOptional upsideFlow Orchestration is now free in Enterprise, Performance, Unlimited, and Developer editions. Review multi-step approval processes or cross-object coordination workflows that could benefit from rebuilding in Orchestration. Exact production upgrade date confirmedRecommendedSetup → Company Information → Instance. Then trust.salesforce.com to find your exact upgrade weekend. Some instances upgraded May 15 — if yours was in that wave, your production org is already on Summer ’26. The items you should do but that will not break immediately 5. Flow Orchestration is now free Flow Orchestration is included in Enterprise, Performance, Unlimited, and Developer editions without usage limits in Summer ’26. If your org has been avoiding Flow Orchestration due to licensing cost, that barrier is gone. Evaluate whether any current multi-step approval processes or cross-object coordination workflows would benefit from rebuilding in Orchestration. 6. Review Agentforce configurations Summer ’26 changes agent lifecycle defaults for orgs running Agentforce in production. If your org has agents in production — even in early access or limited deployment — review the Summer ’26 Agentforce release notes and test agent behaviour in sandbox before production upgrade. 7. Confirm your exact upgrade date Do not assume June 5 or June 12. Your specific upgrade date depends on your Salesforce instance. Check: Setup → Company Information → Instance field. Then confirm your upgrade date at trust.salesforce.com. Some instances upgraded May 15. If your org is on one of those instances and you are reading this on June 4, your production org may already be on Summer ’26. Summer ’26 is the release where “I’ll check the sandbox later” becomes a problem. The June 5 wave is tomorrow. If your sandbox has been on preview since May 8 and you have not looked at it yet, today is the day. Salesforce Admin Summer ’26 Salesforce Release SAML Upgrade Checklist Share: LinkedIn Twitter / X Copy link In this article —Mandatory items 01SAML migration 02Apex security defaults 03Omni-Channel migration 04PDF generation —Recommended items 05Flow Orchestration free 06Agentforce review 07Confirm your date Upgrade dates May 15First wave — already liveCheck if
Standard Omni-Channel Retirement Salesforce
Today is June 1. Standard Omni-Channel in Salesforce is officially retired. If your org has not migrated to Enhanced Omni-Channel Routing and your production instance hits the Summer ’26 upgrade before you are ready, your agents will not be able to log in to Omni-Channel and work items will stop routing entirely. This is not a beta warning. This is now. ⚠What breaks if your org upgrades without completing the migration Agent loginAgents see an error when attempting to log in to Omni-Channel. They cannot set themselves as Available and cannot receive routed work items until the migration is completed. Work routingIncoming cases, chats, and calls stop routing entirely to any queue using Standard Omni-Channel logic. Work items queue without assignment until an admin completes the migration. Specific channelsLive Agent (Chat), standard SMS, and Facebook Messenger queues are the highest-risk channels. Each requires individual migration before Enhanced routing is enabled — enabling Enhanced routing first on these breaks them even if the main switch was working. ResolutionThe fix requires completing migration steps in production under time pressure, potentially during a service outage. The correct time to do this is now, in a sandbox, not after the upgrade breaks routing. Step 1: Check your current Omni-Channel status Open Setup and search for Omni-Channel Settings. If your org shows Standard Omni-Channel Routing as active, you have not completed the migration. If Enhanced Omni-Channel Routing is enabled, check whether all service channels have been migrated — it is possible to have Enhanced routing active but individual channels still on the legacy configuration. The specific channels that require individual migration steps before you enable Enhanced routing are: Live Agent (Chat), standard SMS channels, and Facebook Messenger. Enabling Enhanced Omni-Channel routing before migrating these channels will break routing for those specific queues. Step 2: Check your production upgrade date Not all production orgs upgrade on the same weekend. The Summer ’26 production upgrade runs across three windows: some instances upgraded May 15, the main production wave is June 5, and the final wave is June 12. Your upgrade date determines how much time you have. Find your instance: Setup → Company Information → Instance field. Then check your specific upgrade date at status.salesforce.com. If your instance upgrades June 5, you have four days from today. If it upgrades June 12, you have eleven. How to find your production upgrade date 1Open Salesforce Setup → search for Company InformationSetup → Company Information → Instance 2Note the instance name (e.g. NA87, EU15, AP5) 3Go to trust.salesforce.com → select your instance → find the Summer ’26 maintenance windowtrust.salesforce.com/status/maintenance Summer ’26 Production Upgrade Waves May 15First wave — selected instances already upgraded. If your org is on this wave, you are already on Summer ’26.Already live June 5Main production wave — majority of orgs. This is Thursday. The window to prepare is today.Tomorrow June 12Final wave — remaining instances. You have until June 11 EOD if your instance is in this wave.7 days left Step 3: Migrate in the correct sequence Enhanced Omni-Channel Migration — Correct SequenceDo in this order 1Migrate individual service channels firstLive Agent (Chat), standard SMS channels, and Facebook Messenger must be individually migrated before you enable Enhanced routing. Enabling Enhanced routing before these migrations breaks them. This is the step most orgs get wrong.Do this before anything else 2Enable Enhanced Omni-Channel RoutingAfter channel migrations in Step 1 are complete, open Omni-Channel Settings in Setup and enable Enhanced Omni-Channel Routing. This is the main routing switch — only flip it after Step 1 is confirmed complete.Only after Step 1 3Verify agent capacity model settingsEnhanced routing uses capacity-based logic that may differ from your Standard configuration. Review queue settings and capacity model assignments in your Summer ’26 sandbox. Confirm routing rules behave as expected with simulated work items.In sandbox first 4Test full agent login and work item routing end-to-endHave a test user log into Omni-Channel in the Summer ’26 sandbox, set status to Available, and accept a routed work item through the full flow. Confirm the item closes and activity is logged correctly before applying these settings to production.Verify before production Step 4: Check for exemptions Two specific scenarios may affect your migration timeline. If your org has a legacy Chat implementation that qualified for a legacy-chat exemption, you may have additional transition time — check your org’s Salesforce communication history for any exemption notification. If your org has not yet agreed to Hyperforce AWS terms, certain Enhanced Omni-Channel features may be unavailable until those terms are accepted. If your production org upgrades before this migration is complete: agents will see an error when attempting to log into Omni-Channel, and work items will not route. The fix requires completing the migration steps under time pressure in a production environment. Completing them now, in a sandbox, is the better version of this conversation. Salesforce Admin Omni-Channel Summer ’26 Service Cloud Share: LinkedIn Twitter / X Copy link In this article 01Check your Omni-Channel status 02Find your upgrade date 03Migrate in the correct sequence 04Check for exemptions ⚠ What breaks if you skip this Agents can’t log in to Omni-Channel All work items stop routing Chat, SMS, Messenger break individually Fix in production = outage pressure Migration sequence 1Migrate channels first 2Enable Enhanced routing 3Verify capacity model 4Test end-to-end in sandbox About the Author ST Sergey Trusov CEO & Salesforce Architect at TrueSolv
Salesforce Q1 FY27 Earnings Preview
Salesforce reports Q1 FY27 earnings on June 3. Last quarter: $11.2B in revenue, 29,000 Agentforce deals closed, $800M in Agentforce ARR — and guidance for continued Agentforce-led growth. The question everyone will be watching is not whether the revenue number grew. It is whether Agentforce ARR is accelerating and how many of those 29,000 deals turned into real deployments. Salesforce FY26 Full-Year Results — The Baseline for June 3 Q1 FY27 earnings reported June 3, 2026 after market close $41.5B+10% YoYFY26 full-year revenue — highest annual total in company history $800M+169% YoYAgentforce Annual Recurring Revenue at end of FY26 29,000+50% QoQAgentforce deals closed since launch — commercial and public sector $72BRPORemaining Performance Obligations — contracted future revenue Source: Salesforce FY26 Q4 Earnings, February 25, 2026. Q1 FY27 results on June 3 are the first post-FY26 signal on whether Agentforce momentum is accelerating or plateauing. Watch 1: Agentforce ARR trajectory FY26 closed with $800M in Agentforce ARR after 169 percent year-over-year growth. Q1 FY27 is the first full quarter with three key products in market simultaneously: Agentforce Sales went GA on March 16, Agentforce Operations went GA on April 29, and Agentforce Contact Center is live in Enterprise and Unlimited editions. The ARR number on June 3 is the first clean signal of whether enterprise adoption is compounding from the FY26 base or plateauing as initial deal signings convert into measured deployments. A significant step-up from $800M suggests acceleration. Flat or modest growth suggests the 29,000 deal count is still primarily pilots and signed agreements rather than active production deployments. Additionally, watch the combined Agentforce and Data Cloud ARR figure. In FY26, that number exceeded $2.9B. The Data Cloud layer is the data substrate that makes Agentforce agents reliably useful — its trajectory tells you something about the depth of enterprise adoption beyond surface-level AI feature adoption. Watch 2: Deployment signals versus deal count Twenty-nine thousand Agentforce deals signed is a pipeline number. The more interesting metric is what proportion of those deals moved from signed to live in production. Salesforce provided proxy signals for this in FY26 — token consumption (nearly 20 trillion tokens processed) and agentic work units (2.4 billion delivered) — as evidence of real operational output rather than just signed contracts. Q1 FY27 will either extend those proxy metrics significantly or provide a more cautious signal about deployment pace. Token consumption accelerating quarter-over-quarter is the clearest indicator that the deal count reflects real production usage, not pipeline optimism. Three Questions to Watch on June 3Earnings preview 1 Is Agentforce ARR accelerating from the $800M FY26 base? Q1 FY27 is the first full quarter with Agentforce Sales (GA March 16), Operations (GA April 29), and Contact Center all in market. A significant step-up signals compounding enterprise adoption. Flat growth signals deals are still converting slowly from signed to deployed. Bullish signal: ARR significantly above $800M run rate 2 Are the proxy deployment metrics (tokens, agentic work units) accelerating? FY26 reported nearly 20 trillion tokens and 2.4 billion agentic work units — operational evidence of real production usage. If these numbers step up materially in Q1 FY27, it confirms a meaningful proportion of the 29,000 deals are live in production. Bullish signal: token consumption and agentic work units significantly higher 3 Any signal on Agentforce traction below the enterprise segment? FY26 Agentforce growth was primarily enterprise-led. The Spring ’26 release — AgentExchange consolidation, Salesforce Setup for SaaS, managed package templates — signals intent to accelerate mid-market and SMB adoption. Commentary on sub-enterprise traction would be significant. Watch for: SMB and mid-market Agentforce references in prepared remarks Watch 3: SMB and mid-market traction FY26 Agentforce growth was predominantly enterprise-led. Large deals with named enterprise customers drove the majority of the ARR. The Spring ’26 release — including the Salesforce Setup for SaaS initiative, the AgentExchange marketplace consolidation, and the acceleration of managed package templates for specific verticals — signals intent to bring Agentforce adoption into the mid-market and SMB segments. Salesforce’s $41.5B revenue base was built primarily on SMB and mid-market customers. The long-term Agentforce story depends on whether the platform can deliver agent value at that tier, not just at the enterprise level where implementation complexity is more manageable. One more thing: the Earnings Show format Salesforce moved its earnings calls to a more informal ‘Earnings Show’ format that often includes customer CEO guests and a conversational structure alongside the traditional financial presentation. It is worth watching in full rather than reading the transcript — the customer case studies and Benioff’s commentary on platform direction often contain more signal about where the product is going than the prepared remarks alone. 📺 About the Salesforce Earnings Show — June 3 🕔Time: After market close on June 3, 2026. Typically begins 1 hour after close with the press release, followed by the live show. 🎙️Format: Conversational structure alongside traditional financial presentation. Often includes customer CEO guests discussing real deployment outcomes. 📊Beyond the numbers: Benioff’s commentary on Agentforce deployment depth, customer case studies, and any commentary on the SMB and mid-market motion. 🔗Where: investor.salesforce.com — live stream and replay. TrueSolv will be covering the call live on LinkedIn. The revenue number on June 3 will tell you how Salesforce is doing. The Agentforce ARR trajectory and the deployment signals will tell you whether the platform bet is compounding. Those are different questions and the second one matters more for anyone who depends on Salesforce as infrastructure. Salesforce Earnings Q1 FY27 Agentforce Salesforce News CRM Share: LinkedIn Twitter / X Copy link In this article 01Watch 1: Agentforce ARR trajectory 02Watch 2: Deployment vs. deal count 03Watch 3: SMB & mid-market 04The Earnings Show format FY26 baseline — key numbers $41.5BFY26 full-year revenue $800MAgentforce ARR (end of FY26) 29KAgentforce deals closed $72BRemaining Performance Obligations $2.9BAgentforce + Data Cloud combined ARR June 3 — what to watch 📈Agentforce ARR step-up from $800M ⚙️Token consumption acceleration 🏢Sub-enterprise traction signals 📺Earnings Show — watch in full About the Author DS Daria Savelieva Salesforce Consultant &
Eight Summer ’26 Features Salesforce Developers Should Actually Care About
Summer ’26 release notes landed April 22. Sandboxes upgrade around May 9. If you have not looked at the notes yet, here are the eight features most worth your time — ranked by how much they will actually change your day-to-day development workflow, not by how impressive they sound in the release announcement. Feature Impact Action before May 9 sandbox upgrade LWC Single Component Preview High · GA Test with your most complex custom component. Verify preview correctly reflects nested child component states. No production risk — pure upside for iterative development speed. LWC State Management High · GA Identify pages with multiple LWC components sharing state via prop drilling or message channels. Build a proof-of-concept state store in sandbox before committing to a refactor plan. Collapsible Fault Paths in Flow Medium · GA No action needed before upgrade. Open your largest production flow in the Summer ’26 sandbox to confirm the canvas renders correctly and collapse fault paths for readability. Global Flow Resources Medium · Preview Enable in a preview sandbox. Identify the variables declared repeatedly across your flows. Evaluate the scope of what a GA version could simplify — but do not plan production changes until GA. AI Content Summarizer Component Medium · GA Drop the component onto an Opportunity or Account page in sandbox. Verify Agentforce has data access to the fields that would make the summary useful. Flag gaps for configuration before production. External Client Apps Enforcement High · Act now Open App Manager now. Filter by Connected App type. Identify every Connected App your org created and manages. Confirm migration status to External Client Apps before Summer ’26 tightens enforcement. Web Console for Apex/SOQL Medium · GA Familiarise yourself with the interface in sandbox. Evaluate whether it replaces Developer Console for ad-hoc work or supplements VS Code. Low risk — no configuration required. Agentforce in CRM Surfaces High · Test now Load your production-critical customised pages in the Summer ’26 preview sandbox. Check for layout conflicts between custom Lightning components and new Agentforce-aware UI elements before the upgrade lands in production. 1. LWC Single Component Preview This is the feature that has appeared on Salesforce developer wishlist surveys for multiple consecutive years and finally reached GA in Summer ’26. The ability to preview a single Lightning Web Component in the browser or in VS Code without triggering a full page reload is not a small improvement — it removes one of the most consistent time sinks in iterative LWC development. The practical impact depends on how much LWC work you do. For a developer spending four hours on a component UI, the difference between a 90-second page reload and an instant preview compounds significantly across a day. For teams building complex component libraries, the impact is considerable. GA means it is stable, supported, and safe to rely on in production development workflows. Test it in your Summer ’26 sandbox first to confirm it behaves correctly with your component architecture. 2. LWC State Management State Management for LWC reaches full general availability in Summer ’26, providing centralised state across component trees — the standard pattern for managing shared state in modern frontend development that LWC has been missing. The practical scenario: an Opportunity detail page has a line items component, a totals component, and a discount component. All three need to respond to the same underlying deal data. Without State Management, this requires lifting state through the parent component via properties, creating a coordination pattern that grows increasingly unwieldy as component trees deepen. With State Management, each component subscribes to a shared store directly. Before — prop drilling across components // Parent must hold all shared state // and pass down as props to each child @track totalMrr = 0; @track discount = 0; @track finalPrice = 0; // Wired to LineItems via: <c-line-items total-mrr={totalMrr} discount={discount}> </c-line-items> // And to Totals separately… // Grows unwieldy fast. After — centralised state store // Shared store — declared once import { createStore } from ‘@salesforce/state’; export const oppStore = createStore({ totalMrr: 0, discount: 0, finalPrice: 0 }); // Each component subscribes directly // No parent coordination needed // LineItems, Totals, Discounts // all update from the same store 3. Flow UI: Collapsible Fault Paths and Readable Data Tables Collapsible fault paths extend the canvas cleanup work started in Spring ’26 with collapsible Decisions and Loops. Large production flows become difficult to maintain when fault paths branch from every element that can fail and the canvas is an unnavigable tangle of error-handling logic. For developers maintaining flows built by previous admins, collapsible fault paths are a significant cognitive load reduction. The execution path becomes readable when error handling is collapsed. When debugging, expand the specific fault path you are investigating rather than navigating around all of them simultaneously. The data table display improvements in Flow Builder are in the same category — cosmetic in that they do not change flow behaviour, but meaningful for any developer who has tried to read a data table in the current canvas and given up. 4. Global Flow Resources Still in preview orgs, but worth testing now: Global Flow Resources enable variables and components to be shared across flows platform-wide rather than redeclared in every flow that needs them. The impact depends on your org’s automation architecture. Orgs with dozens of flows that each declare the same custom picklist variable or the same error-handling configuration are the immediate beneficiaries. If this ships as expected in Winter ’27 based on the current preview, it significantly reduces duplicated logic across complex automation layers. Because it is in preview, it belongs in your summer sandbox testing but not in your production planning until GA is confirmed. 5. AI Content Summarizer Component A new AI Content Summarizer component can be dropped onto any Lightning record page from App Builder without writing Apex. It surfaces an Agentforce-generated summary of the record’s key information — account history, deal context, case background — directly on the page. The developer
Agent Script: The Layer Between AI Flexibility and Enterprise Control
The biggest complaint about AI agents in production has always been the same: they work great in demos and go off-script in real deployments. Salesforce heard that complaint and built Agent Script — a scripting language that lets you define exactly how an agent behaves, step by step, without giving up the flexibility that makes AI useful. Here is what it is, how it works, and why it changes the calculus on Agentforce adoption. Agent Behaviour: Without vs. With Agent Script WITHOUT Agent Script — probabilistic path WITH Agent Script — deterministic rails User request Path A Path B Path C Outcome depends on reasoning and conversation flow ⚠ Risk: agent may skip required verification if the user’s phrasing is persuasive or impatient User request Identity verified REQUIRED STEP — Agent Script AI handles response Verification tool call must return confirmed — no bypass ✓ Deterministic: required steps always execute AI reasoning operates within defined rails The problem Agent Script was built to solve AI agents are probabilistic systems. Give an agent a task and it reasons toward an outcome — evaluating options, choosing actions, interpreting ambiguous inputs — in a way that is flexible and often impressive but never fully predictable from the instruction set alone. For customer service, sales qualification, and internal help desk use cases, that flexibility is valuable. The agent can handle variations in how a question is asked, adapt to unexpected inputs, and reach correct outcomes through different reasoning paths. However, for enterprise deployments where specific steps must happen in a specific order — identity verification before account access, compliance disclosure before a financial recommendation, escalation to a human at a specific deal stage — probabilistic behaviour is a blocker, not a feature. The question is not whether the agent gets to the right answer. It is whether it follows the required path to get there. How Agent Script works Agent Script adds a deterministic layer on top of the AI reasoning layer. You define the fixed logic in a human-readable JSON expression language — the if/then rules, the required tool calls, the handoff triggers, the compliance checkpoints — and the LLM handles the conversational reasoning in between the defined steps. The mental model is a set of rails. Between the rails, the agent reasons freely and handles variation naturally. At the defined points on the rails, the behaviour is fixed: the agent must perform a specific action, verify a specific condition, or hand off to a specific resource before it can continue. Agent Script — identity verification before account access Simplified example // Step 1: Required identity verification // Agent cannot proceed until this returns “verified” { “step”: “verify_identity”, “type”: “required_tool_call”, “tool”: “IdentityVerificationService”, “condition”: { “result”: “verified” // must match — no bypass } } // Step 2: AI handles the response conversation // LLM reasoning operates freely here { “step”: “handle_account_query”, “type”: “llm_reasoning”, “context”: “account_data”, “guardrails”: [“no_pii_in_response”] } // Step 3: Handoff trigger if deal threshold met { “step”: “check_escalation”, “if”: { “deal_value”: { “$gt”: 50000 } }, “then”: { “action”: “handoff_to_human”, “queue”: “senior_sales_rep” } } Between the defined steps, the AI reasons freely. At the defined steps, the behaviour is fixed — the agent cannot proceed without completing the required action. The distinction from a traditional decision tree is important. Agent Script is not replacing AI reasoning with a flowchart. It is constraining the parts of the interaction where constraint is required while leaving the parts where AI is valuable free to operate as designed. Practical examples Customer service agent with identity verification Without Agent Script: The agent is instructed to verify identity before accessing account data. Whether it follows that instruction precisely depends on how the conversation goes — a persuasive or impatient customer might cause the agent to skip or abbreviate the step. With Agent Script: Identity verification is a defined step in the script. The agent cannot proceed to account lookup until the verification tool call returns a confirmed result. The LLM handles the conversation around verification, but the verification itself is not optional. Sales qualification agent with human handoff Without Agent Script: The agent is instructed to hand off to a human sales rep when a qualified opportunity reaches a specific threshold. Whether it recognises the threshold correctly depends on its interpretation of the conversation. With Agent Script: The handoff trigger is defined explicitly. When the deal value field exceeds the threshold, or when the prospect uses specific phrases indicating high purchase intent, the agent executes a defined handoff action to the Salesforce queue. The LLM does not decide whether the handoff happens; the script does. Integration with Agentforce Builder Agent Script integrates with Agentforce Builder — the conversational build environment introduced in Spring ’26. Admins and developers write Agent Script in the Builder interface alongside the natural language instructions that govern the agent’s conversational behaviour. The separation of concerns in the build environment mirrors the separation in the runtime: conversational behaviour is configured in natural language, deterministic controls are written in Agent Script. Neither replaces the other. Additionally, Agent Script was open-sourced at TDX 2026. The full specification, parser, and compiler are on GitHub. For compliance teams and legal teams who need to understand and audit agent behaviour independently of the vendor, this is significant: Agent Script is a readable, auditable format that does not require Salesforce expertise to understand the logic. Who needs Agent Script now, and who can wait Use case type Determinism non-negotiable Pure AI reasoning is fine Customer service — account access Identity verification must precede account lookup without exception. Agent Script enforces the required step regardless of conversation flow. Handling FAQ questions that do not involve personal data — product information, store hours, general policies. Financial services Regulatory disclosures must be delivered before a product recommendation. Compliance checkpoints cannot be skipped regardless of conversation length. Summarising publicly available market information with no personalised recommendation required. Sales qualification Handoff to a human rep must trigger at a specific deal stage or value threshold,
Summer ’26 Flow Updates: Six Things That Will Actually Change How You Build Automations
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. Summer ’26 — New Flow Date Operators Quick Reference Is Today Matches records where the date field equals the current date. Ideal for daily-run flows that flag due-today tasks, contracts expiring today, or time-sensitive SLA conditions. Is Tomorrow Matches records where the date field equals tomorrow’s date. Use for advance notification flows — renewal reminders, follow-up triggers, appointment confirmations the day before. Is On Matches records where the date field equals a specified date or relative date formula. Most flexible of the new operators — covers “is on the first of next month” and similar calculated dates. Anniversary Matches records where the month and day of the date field match the current month and day, regardless of year. Use for birthday campaigns, contract anniversary workflows, and renewal sequences tied to the same calendar date each year. ⚠ Important: these operators apply to Date fields only — not DateTime. Check your field type 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