#release-notes — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #release-notes, aggregated by home.social.
-
What’s Different in pnpm 12, by @kochan.io (@pnpm):
https://pnpm.io/blog/whats-different-in-pnpm-12?ref=frontenddogma.com
-
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
Including apps for tracking alcohol consumption. 🥴
— Zawinski’s Law, 1995
#ReleaseNotes -
The Ultimate Guide to Salesforce Flow in Winter ’27
In automation circles, the question always comes up: Does Salesforce do a good job with improving the Flow product? Or are the resources working on Agentforce instead of now legacy products like the Flow Builder? I will leave the answer to you. Please make your own assessment after you go through all the improvements that are coming in Winter ’27.
In this release, Salesforce has delivered some of the anticipated, developer-grade enhancements for the Flow Builder. From canvas UI/UX overhauls and efective error diagnostics to fully isolated testing environments and next-gen screen flow features, Winter ’27 is set to improve how administrators and developers build, test, and scale their automation.
In this deep dive, we will unpack the top new Flow features in Winter ’27 and explore how you can use them to build highly resilient, enterprise-grade automations.
Modernizing the Canvas: UI & UX Upgrades
Designing flows has always been a highly visual process. In Winter ’27, Salesforce has completely modernized the Flow Builder canvas to align with the rest of the Salesforce ecosystem, significantly improving day-to-day productivity.
Experience Flow Builder in the Modern Salesforce Cosmos Theme
Flow Builder now boasts a visually consistent, up-to-date look by integrating the modern Salesforce Cosmos theme. This theme automatically respects your organization’s active theme without requiring any manual setup or administrative configuration. The Cosmos theme brings increased spacing, a refined color palette, and visual consistency across all designer pages. Note: Flow Builder does not support Salesforce Lightning Design System (SLDS) 2 Dark Mode at this time.
See More with a Denser Canvas
To reduce the tedious “scroll and zoom” dance required when managing large automations, the Flow Builder canvas is now significantly more compact.
- Compact Element Cards: Visual clutter has been minimized. Individual element cards on the canvas are smaller but show the element’s type and API name inside an elegant info tooltip when you hover over them.
- End Element Icons: The end of a flow is no longer represented by a full card. It has been converted into a simple, clean icon, making it immediately clear that there is nothing to configure.
Track Changes Over Time with Edit History
One of the most requested features in Flow history is finally here! For flows that support versioning, you can now open a dedicated Edit History panel to view a chronological timeline of every single save within the current version. This feature allows you to:
- View a timeline of saves and preview what changed in each save.
- Drill down into element-level details to see exactly which elements were modified.
- Revert to previous logic by selecting Save as New Version to restore a past instance, or select Save as New Flow to copy your legacy logic into a separate, clean flow.
Clean Up Instantly with the Unused Resources Filter
Over time, as requirements change and flows are refactored, unused variables, collections, and formulas build up, cluttering the Toolbox. You can now use the new Unused filter in the Flow Builder Toolbox. Selecting this filter narrows the list of variables down to only those with no recorded usage in the active flow, allowing you to quickly delete them and keep your metadata clean. This feature is available exclusively in auto-layout mode.
Navigate Flow Comparison Results More Easily
Tracking differences between versions has never been cleaner. The Flow Version Comparison tool now features a more streamlined results view.
- Clickable Elements: Element name labels in the comparison table are now clickable and open a resizable side panel containing complete, detailed change records. This makes auditing changes significantly faster.
- Reduced Clutter: The “Change Details” column has been removed from the comparison table to maximize screen real estate.
- Logical Version Ordering: The selection dropdowns now list flow versions in a clear, logical chronological order.
- Expanded Support: Version comparison is now also supported for Data 360-triggered flows and Agentforce Marketing flows (including segment-triggered, automation event-triggered, and API event-triggered flows). This works across all audience sources in segment-triggered flows and shows changes in both table and canvas views.
Seamless Decision Element & Keyboard Navigation
Managing complex branching is much smoother. You can now configure Decision elements with path highlighting, resizable panels, and inline path renaming. Clicking a canvas path instantly highlights its corresponding outcome in the property panel. You can resize the property panel to see more details, and simply double-click a path name directly on the canvas to rename it without opening the full property panel.
Furthermore, you can navigate the entire auto-layout canvas hands-free using your keyboard’s arrow keys to jump from element to element, including across branching and fault paths. You can also cut, copy, and paste elements using standard operating system keyboard shortcuts, making restructuring a breeze.
End Elements Saved to Metadata
Previously, flow metadata did not explicitly include the end elements, meaning the canvas layout was reconstructed every time a flow was opened, leading to canvas reshuffling. Flow Builder now automatically saves end elements to your flow’s metadata whenever you save in autolayout, ensuring your canvas layout stays exactly as you left it. This also gives external metadata and CI/CD tools complete visibility into where your flow ends. I love this new addition.
Proactive Error Prevention & Resilience
Production failures are expensive and disrupt business continuity. Winter ’27 shifts error handling from “reactive debugging” to “proactive defense” by validating configuration rules at save-time and making runtime processing far more resilient.
Save-Time Field Length Validation
We have all faced a flow crash due to a text value exceeding the maximum character length of a target field. Now, when you save a flow, Flow Builder automatically validates fixed-text field length constraints in your Assignment elements. If you attempt to assign a fixed-text value that exceeds the target field’s maximum length, a warning appears in the validation panel. This allows you to resolve the configuration issue before activation. Note that this validation checks fixed text and does not support dynamic variable references since their values are unknown until run-time.
Catch Missing Required Fields on Save
To prevent empty insertions, Flow Builder now warns you at save-time if a Create Records element utilizing a record variable is missing an assignment for a required field. Previously, these missing required fields were only discovered during run-time failures. The validation runs automatically upon saving and highlights the exact missing assignment in the validation panel
Reduce Scheduled Flow Failures with Dynamic Batch Sizing
Scheduled flows running against large datasets frequently fail when encountering system governor limits (such as CPU time, SOQL query, or heap limits). Winter ’27 introduces dynamic batch sizing for scheduled flows and scheduled paths. When enabled in the Start element configuration, if a batch run hits a CPU, SOQL, or heap limit, the system automatically retries the operation by halving the previous batch size. It continues halving the batch size until it finds a volume it can successfully process without a limit error, and then completes the remaining records in batches of that newly determined size. This is a very exciting feature, perhaps a sign of what is to come in regards to self-fixing automation.
Automatic Retries for Record Lock Contention
Database row locking is a common pain point in highly automated environments, causing transaction failures with UNABLE_TO_LOCK_ROW errors. In Winter ’27, flows automatically retry when they encounter a record lock error during transaction initialization. If a record is temporarily locked by another process, the flow automatically pauses for 10 seconds and retries the operation, giving the conflicting transaction enough time to complete and release the lock. Another awesome feature that will decrease errors, especially for schedule-triggered flows.
Modern Screen Flows & Dynamic User Interfaces
Screen Flows get a massive boost in Winter ’27, making them far more dynamic, responsive, and suited for high-volume operations.
Run Screen Flows on Multiple Selected Records from List Views
Administrators can now configure a screen flow as a mass quick action on list views and related lists. This allows users to select up to 2,000 records from a data table and pass all selected record IDs directly into a single screen flow to execute bulk operations. You no longer need complex custom Apex or Visualforce workarounds to process list selections. Simply create an action of type Flow, add it to the List View Button Layout, or assign it to a related list in Page Layouts. I was asked this feature more than once by clients. Now I can deliver.
Your multiple record screen flow list view action now runs in a clean modal.The New Time Screen Component
You no longer have to build custom components or use text fields to capture time values. Winter ’27 introduces a standard Time component for Flow screens. This component allows you to:
- Capture precise time values for service appointments, scheduling, and reservations.
Set placeholder text. - Enforce minimum and maximum time boundaries directly within the properties panel to restrict user selections.
Reactive Formulas in Conditional Visibility
Salesforce continues to advance Screen Flow Reactivity. You can now reference reactive formulas directly in your screen conditional visibility rules. Previously, conditional visibility did not support referencing formulas that contained components on the very same screen. With this update, formulas evaluate in real-time as users interact with screen components, dynamically showing or hiding fields on the fly. Another feature I wished existed before this release. Great news.
Testing & Diagnostics in Isolation
Testing automations has traditionally been a tedious process of manually creating records, running debugs, and cleaning up test data. Winter ’27 entirely changes the testing landscape.
Experience the Dedicated Flow Test Mode (Beta)
You can now toggle between building a flow and testing it in a single, dedicated workspace with Flow Test Mode (Beta) for record-triggered and autolaunched flows.
Image source: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_test_mode.htm&release=264&type=5When you click Test in Flow Builder, the canvas switches to a test view where you can configure inputs, set triggering records, and define assertions (expected outcomes that report pass or fail).
Once a test run completes successfully, you can save the setup as a reusable Test Scenario. You can run these saved scenarios at any time with a single click, allowing you to instantly verify that your flow still works after making modifications.Mock Outputs for HTTP Callouts and Subflows (Beta)
Testing flows that invoke external REST APIs or deep subflows has always been highly unpredictable because it required live connections or complete subflow executions. Winter ’27 solves this with Mock Outputs for Action and Subflow elements (Beta).
Image source: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_test_mock_output.htm&release=264&type=5When you mock an HTTP callout Action element, the test run skips the actual REST request and returns your pre-defined mock response. When you mock a Subflow element, the execution of the referenced subflow is skipped, and the parent flow uses the mock outputs you specify. This allows you to safely test rate-limited APIs, complex Apex dependencies, and tricky fault paths without writing a single line of Apex test mock code.
AI-Generated Tests with Agentforce for Flow
Want to skip the manual setup of test cases? Let AI do the heavy lifting! Using Agentforce for Flow Headless, you can generate comprehensive test scenarios directly from your command-line terminal without opening Flow Builder.
Connect your terminal to your Salesforce org, navigate to the flow, and enter the prompt: create flow tests.
Agentforce analyzes your flow’s logic branches and automatically generates test scenarios covering success, fault, and edge-case paths.You can also run the prompt use isolated data for my flow tests to have Agentforce automatically spin up isolated test data that runs independently of your org data, protecting production integrity.
Enhanced Debugger: Collection Inputs & Static IDs
Debugging in Flow Builder is much more powerful:
- Static Record IDs: You can now input a static 15-character or 18-character record ID directly into the debugger panel to debug objects with limited searchability, such as Cases or Campaign Members.
- Primitive & Record Collections: You can now populate entire primitive and record collections inside the debugger input variables to test multi-record scenarios, avoiding the old limitation of only being able to test single input values. These changes will definitely make my life easier.
Enterprise Scaling, Governance & Approvals
For enterprise environments managing thousands of users and complex transaction cycles, Flow in Winter ’27 introduces crucial architectural upgrades and metadata-level governance.
Classify and Discover Flows with Flow Tags
As flow libraries grow into the hundreds or thousands, keeping automations organized using naming conventions alone is incredibly difficult. Winter ’27 solves this with Flow Tags—a structured classification system that lets you label and organize your automations.
- Automation App Tags Tab: Go here to create tags and arrange them into logical tag groups (e.g., by department, team, or business domain).
- Bulk or Row-Level Tagging: From the Flows tab, tag flows individually or in bulk using the Assign Tags action. You can also assign tags in Flow Builder via the Save As modal.
- Filtered Discoverability: Filter the flow list directly by one or more tags to instantly surface related automations.
The Request Approvals Component (Now Supports Up to 10 Processes)
You can now add the new Request Approvals component directly to your Lightning record pages or Experience Builder sites, giving users a selection of up to 10 autolaunched flow approval processes to choose from when submitting a record. This provides unprecedented flexibility for records that require different approval matrices depending on business context.
Automatically Open the Next Work Item
To keep users focused and eliminate navigation clicks, you can enable the Automatically Open Next Work Item option on the Orchestration Work Guide. When a user finishes approving a work item, the component automatically opens the very next work item in the same running approval process or orchestration, keeping them in their flow without returning to a list view.
Routing Record-Change Events to a Dedicated Channel
In high-volume orgs, bulk data operations (like data loads) would trigger thousands of record-change platform events, which queued up in the same channel as flow approval step-completion events. This often stalled running flow approval processes and delayed work items. In Winter ’27, Salesforce automatically routes record-change events to a dedicated channel, separating them from step-completion traffic, ensuring approval processes remain highly responsive under bulk load.
Run Flows Explicitly in User Context
Security is paramount. Winter ’27 introduces a new runtime setting: User Context – Enforces User Permissions. When configuring a flow’s run-time properties, selecting this setting ensures that the automation strictly enforces the running user’s object-level permissions, field-level security, and sharing rules, regardless of how the flow was launched.
Get Ready for Winter ’27
The Salesforce Winter ’27 Flow updates represent a big shift toward enterprise-grade resilience, design productivity, and robust testing standards. By shifting diagnostics to save-time, providing automated batch and lock retries, and giving us developer-class testing tools like Mock Outputs and Agentforce CLI generation, Salesforce is ensuring that our automations are built to succeed from day one.
These features are currently in preview, with rolling upgrades arriving in sandboxes and non-production environments according to the official Salesforce release schedule.
Which Winter ’27 Flow feature are you most excited to implement in your org? Let us know in the comments below on Salesforce Break!
Explore related content:
11 Flow Updates in Summer 26 Release
Agentforce Agent Flow Action Best Practices
Should You Use Roll Back Records in Salesforce Screen Flows?
#Agentforce #AI #Automation #ReleaseNotes #SalesforceAdmin #SalesforceDeveloper #SalesforceUpdate #Winter27 -
What’s New in Astro—July 2026, by @sarah11918:
https://astro.build/blog/whats-new-july-2026/?ref=frontenddogma.com
-
via @dotnet : .NET 11 Preview 7 is now available!
https://ift.tt/JbBh9yN
#NET11 #Preview7 #dotnet #dotnet11 #ReleaseNotes #Libraries #Runtime #SDK #CSharp #ASPNetCore #NETMAUI #EntityFrameworkCore #EFCore #FSharp #WindowsForms #WebAssembly #JIT #NativeAOT #Seria… -
Squeak/Smalltalk 6.1 Release Notes
https://squeak.org/release_notes/6.1/
Comments: https://news.ycombinator.com/item?id=49242653
#HackerNews #Squeak #Smalltalk #ReleaseNotes #Programming #Community
-
vlt 1.0 and Hosted Package Registries, by @darcyclarke.me (@vlt.io):
-
What’s New in Svelte: August 2026, by @dreamindani (@sveltejs):
https://svelte.dev/blog/whats-new-in-svelte-august-2026?ref=frontenddogma.com
-
pnpm 11.11–11.14, by @kochan.io (@pnpm):
https://pnpm.io/blog/releases/11.11-11.14?ref=frontenddogma.com
-
Introducing shadcn/typeset, by (not on Mastodon or Bluesky):
-
Monday, July 27, 2026 Security Releases, by @nodejs:
https://nodejs.org/en/blog/vulnerability/july-2026-security-releases?ref=frontenddogma.com
-
Safari Technology Preview 248 Released
https://webkit.org/blog/18162/release-notes-for-safari-technology-preview-248/
Comments: https://news.ycombinator.com/item?id=49013356
#HackerNews #SafariTechnologyPreview #WebKit #ReleaseNotes #BrowserUpdates #TechNews
-
Next.js Security Release and Our Next Patch Release, by (not on Mastodon or Bluesky):
-
Announcing Vite Beta, by @manniL and others (@voidzero.dev):
https://voidzero.dev/posts/announcing-vite-plus-beta?ref=frontenddogma.com
-
What’s New in Svelte: July 2026, by @sveltejs:
https://svelte.dev/blog/whats-new-in-svelte-july-2026?ref=frontenddogma.com
-
My latest app, Changelogs, is now on the App Store.
- Track updates for your favorite apps and get notified when new versions are released.
- Review latest release notes with swipeable cards interface.
- Revisit seen releases in a growing timeline.
- Export your tracked apps for backup or sharing.This project started over 4 years ago, and I’m happy to finally share it. Enjoy!
https://apps.apple.com/pl/app/changelogs/id6758763193?uo=4
https://changelogs.thanel.me -
Announcing TypeScript 7.0 RC, by @danr.bsky.social:
https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-rc/?ref=frontenddogma.com
-
Node.js 26.4.0 (Current), by @aduh95.bsky.social (@nodejs):
https://nodejs.org/en/blog/release/v26.4.0?ref=frontenddogma.com
-
Visual Studio 2026 Version 18.7.2 Release Notes | Microsoft Learn
https://learn.microsoft.com/visualstudio/releases/2026/release-notes#18.7.2
#visualstudio #vs2026 #releasenotes #dotnet #githubcopilot #productivity
-
Firefox 152 Release Notes for Developers (Stable), by @mdn:
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/152?ref=frontenddogma.com
-
My cohost @mkohn was complaining about how useless Slack release notes are, and I have to agree that, in general, all app store release notes are useless. But your asking me to use my bandwidth to update the app, you should at least have the decency to let me know why. This isn't just a Slack problem, this is everyone do better. #appstore #releasenotes
https://slack.com/release-notes/mac
I get that a lot of small releases aren't that interesting, but I still appreciate them. @SlackHQ
-
Releasing Babel 8 Today: ESM-Only, Drop ES5 Default, and a Smooth Migration Path, by @babel.dev:
https://babeljs.io/blog/2026/06/16/8.0.0/?ref=frontenddogma.com
-
Lying in bed at 6:25 am reading #releasenotes for #HomeAssistant and #Haos…. Totally normal Saturday right?
-
Junie: The JetBrains AI Coding Agent Leaves Beta, by @jetbrains.com:
https://blog.jetbrains.com/junie/2026/06/junie-coding-agent-out-of-beta/?ref=frontenddogma.com
-
HTML Minifier Next 7 Is ESM-Only, by @j9t [@frontenddogma]:
https://meiert.com/blog/html-minifier-next-7/?ref=frontenddogma.com
-
Announcing Angular v22, by @angular.dev: