Why Release Notes Get Ignored

Salesforce release notes are long. A given release can run a thousand pages covering every cloud, every feature, every tweak. Admins and developers rarely have time to read them all.

This article distills Spring ‘26 to what actually affects your day-to-day — the changes worth time-blocking, the changes to know about casually, and the ones you can safely skip.

Agentforce and AI

Agentforce 2.0 Expanded

The biggest theme. Spring ‘26 shipped the expanded Atlas reasoning engine with multi-step plan-act-observe-revise loops. Agents handle ambiguous multi-part requests materially better than 1.0.

Other Agentforce updates:

  • Richer standard action library.
  • Improved Data Cloud grounding integration.
  • New channels and message surfaces.
  • Evaluation API improvements for programmatic testing.

If you deployed on 1.0, evaluate 2.0 behavior against your existing test set before expanding scope.

Prompt Builder Enhancements

  • Better template versioning.
  • Enhanced debugging surface with step-by-step prompt evaluation.
  • Additional pre-built templates in the gallery.

If you’re building prompt templates, the workflow is noticeably better.

Einstein Trust Layer Tightening

Default masking rules became stricter. Review any prompt outputs that now contain mask tags — you may need to selectively loosen rules or update prompts.

Data Cloud

Zero-Copy Federation Expansion

Support for additional warehouses (expanded Snowflake, Databricks, BigQuery scenarios). Additional query performance improvements.

If you’re considering Data Cloud + warehouse federation, this release is a good evaluation point.

Streaming Insights GA

Streaming insights — real-time computed metrics — moved to general availability in Spring ‘26. Use cases in real-time personalization, fraud detection, ad bidding.

Evaluate carefully: streaming insights cost meaningfully more than batch equivalents. Ensure the use case demands real-time before adopting.

Identity Resolution Improvements

Tuning and reliability improvements to identity resolution rulesets. Minor, but worth re-running your rulesets post-release to see if merge ratios shift.

Flow

Flow Test Enhancements

More scenarios supported by Flow Tests, better CI integration. If you haven’t adopted Flow Tests, this release is a good excuse.

Scheduled Paths Improvements

Scheduled paths in record-triggered flows gained more control over timing and reprocessing. Review existing scheduled paths for opportunities to simplify.

Visual Flow Builder UI Refinements

Better navigation on complex flows, improved debug output rendering, minor ergonomic improvements. Nothing breaking; nicer to live in daily.

Platform Developer Experience

Source Format Enhancements

Minor improvements to SFDX source format handling of specific metadata types. Less manual editing required after retrieves.

Apex Scripting Enhancements

Anonymous Apex and script execution received updates — bigger heap allowances in specific contexts, better error surfacing.

CLI Updates

sf CLI stability fixes, performance improvements on large metadata retrieves, better scratch org diagnostics.

Admin and Configuration

Dynamic Forms Rollout

Dynamic Forms support continues expanding to more standard objects. Check if your target object is newly supported.

Permission Set Groups Improvements

Better UI for managing PSGs, clearer audit reporting of PSG-derived permissions.

Flow Orchestrator Enhancements

Additional step types, better reassignment and escalation controls. If you’re running orchestrations, review the new step options.

Service Cloud

Case Escalation Rule Improvements

Finer-grained controls, better integration with Agentforce-triggered flows.

Knowledge Updates

Better Knowledge rendering in Agentforce responses; more flexible article versioning.

Sales Cloud

Forecasting Enhancements

Improved forecast category handling, better cross-hierarchy visibility for managers.

Opportunity Enhancements

New standard fields in some editions, improved duplicate-flow handling.

What Got Deprecated

Ongoing retirement themes:

  • Legacy Workflow Rules: progressive end-of-life. If you still have production Workflow Rules, this is the release to finish your migration.
  • Process Builder: same.
  • Older Aura components: Salesforce continues to signal LWC as the default path. Audit heavy Aura dependencies.

None of these were “turned off” in Spring ‘26, but the pressure continues.

Release Management Recommendations

For most orgs:

  • Update your sandbox with the Spring ‘26 preview version.
  • Run your test suites (Apex, Flow Test, regression).
  • Test critical user journeys manually.
  • Review any Agentforce agents against new Atlas behavior.
  • Monitor for 2–4 weeks post-prod-release before adopting new features aggressively.

Features to Plan Time For

Prioritize evaluation time for these:

  1. Agentforce 2.0 and Atlas improvements. Test existing agents against the new reasoning behavior.
  2. Streaming Insights if you have real-time CDP needs.
  3. Trust Layer default changes. Verify no existing prompts now produce mask-tag-leaked output.
  4. Flow Test updates if you haven’t adopted.

Features Safe to Skip for Now

  • Many UI tweaks in niche areas (won’t affect day-to-day).
  • Deprecation warnings that don’t trigger for 2+ releases.
  • Pilot features (not GA; unstable contract).

You can come back to these later without penalty.

Frequently Asked Questions

When does Spring ‘26 reach my production org?

Salesforce stages releases in waves. Check the release calendar on Salesforce Help. Typically Spring releases complete by early February; Spring ‘26 may adjust slightly per actual Salesforce schedule.

What’s the difference between Preview and Patch?

Preview (pre-release) is 4–6 weeks ahead of GA for sandboxes that opted in. Patches are ongoing fixes after GA.

How do I know if a feature is GA, Beta, or Pilot?

Release notes mark each feature with its availability status. Only build production on GA features.

Can I opt out of a release?

No — releases are applied to every org within a window. You can only delay updates to Sandboxes used for preview testing.

Share