You will get a reusable postmortem template for Salesforce incidents, with the org queries to rebuild the timeline and a method for finding where warnings were lost.
Build the timeline from org records
Search tickets and chat for earlier warnings
Ask each person individually what they saw
Record contributing factors by role, not name
Assign each change an owner and a due date
The order in which a blameless postmortem is built, as the article describes it
The author argues that when a Salesforce production incident happens, the first question is often who deployed, which discourages people from speaking up. A blameless postmortem instead asks how the process let the problem through and whether anyone saw it coming. The piece offers a template with sections for the incident summary, timeline, what the team knew beforehand, contributing factors, and a changes table with owners and due dates. Two rules keep it blameless: names appear only in the timeline, never in contributing factors, and every action needs an owner and a date.
To build the timeline from the org, the article points to Setup Audit Trail, which can be queried with SOQL on SetupAuditTrail for the last seven days or exported with the Salesforce CLI. It also suggests checking Setup > Deployment Status for recent deployments and their initiators, and Flow and Apex error emails for exact timestamps and failing elements. If nobody receives those error emails, the author says that gap itself belongs in the changes table.
The section on what the team knew before is presented as the most important part. The author recommends searching tickets, pull request comments and chat threads, then asking people individually whether they noticed a concern and whether they raised it. Where a warning was raised but lost, the document should say so plainly, since it shows where the process drops warnings. The article closes with tips for running the review meeting, such as having the most senior person speak last.
You will understand how Flow Orchestration organizes stages and steps across automated and interactive work, and when it is better than chaining several Flows.
Why read this
The article gives a worked onboarding example and a short checklist for a first build.
Automated Flow stage
Interactive Screen Flow stage
Automated provisioning stage
A Flow Orchestration advances to the next step only when the previous one completes
Most automations start as one Flow, but as a process grows, several Flows can conflict, run out of order or duplicate work. Flow Orchestration, which the article describes as generally available in recent releases, lets you build one process made of stages and steps, where each step is an automated Flow, a background Apex or invocable action, or an interactive Screen Flow or approval assigned to a user or queue with a due date.
An orchestration advances to the next step only when the previous one completes. If a step fails, the orchestration pauses rather than continuing silently, and the orchestration run record shows the current stage, step, assignee and status in one place. The author’s onboarding example has an automated stage that creates tasks and a project, an interactive stage where a specialist confirms a kickoff call within three days, and an automated stage that provisions a portal user and sends a welcome email.
The article says orchestration suits processes with handoffs between people and automation, such as approvals, onboarding, case escalation and quote-to-cash, and is excessive for a single condition-and-action rule. It advises mapping the process on paper first, keeping one job per Flow, and remembering that orchestration runs consume Flow interviews and so still need governor-limit planning.