Field notes on the Spring ’26 critical update.
Working notes on the Spring ’26 outbound-message session-ID removal — what broke, what to look for in your org, and how the auto-patcher fits. The diagnostic at /connect is free; the paid bundle is $299 one-time per org.
Spring '26 Session-ID Removal — What Changed and Who's Affected
Spring '26 stopped populating the <sessionId> element in Salesforce outbound message payloads (enforced Feb 23, 2026). Quick reference: what changed, what breaks, what to look for in your org, and how to fix it.
Inside the Spring '26 Outbound Message Session-ID Removal — A Technical Deep-Dive
What Spring '26 actually changed in Salesforce outbound message payloads, why session-ID auth broke, and how to migrate Apex callouts and downstream listeners to Named Credentials, signed payloads, or shared secrets.
Salesforce Outbound Message Session-ID Fix — What Broke, How to Patch It
Salesforce outbound messages no longer include a usable session ID after Spring '26 (Feb 23, 2026). Here's what to change in your workflow XML, your Apex callouts, and your downstream listener — with a free diagnostic and a paid auto-patcher.
Salesforce Critical Update Patch — Generated Code, Not Just Impact Reports
Existing Salesforce release tooling tells you what will break. The Critical Update Auto-Patcher generates the patched Apex, workflow XML, and Apex test scaffolds for the named breaking change — currently the Spring '26 outbound-message session-ID removal.
For operators — distribution material
Reply templates for Trailblazer Community / Salesforce Stack Exchange, r/salesforce, and LinkedIn live in content/reply-templates/ in the repo. Each template includes posting etiquette, a short and long form, and a truthfulness checklist that mirrors CriticalPatcher Constraints.md.