Keep orchestration visible
Flow owns business-readable sequencing while specialized routing stays behind one Apex action.
All builds
FLOW ORCHESTRATION
Flow Rescue Lab
A tangled request process rebuilt as visible orchestration with reusable paths, metadata-driven SLA policy and an auditable failure route.
Record-triggered FlowSubflowCustom MetadataScheduled PathApex action
Interactive demo
Launch the demo Sample build using synthetic data in a Developer Edition org. Created to demonstrate architecture and delivery approach; not presented as client work.
The scenario
A designed problem, not a client claim.
DemoCo requests arrive without consistent ownership, due dates or recovery behavior. Business rules are difficult to inspect, and exceptions rely on manual follow-up.
Before · Messy process
- Intake fields can be incomplete or inconsistent.
- Routing, SLA and updates are coupled in one path.
- Faults do not preserve enough context for recovery.
- Escalation can run without checking the latest Case state.
After · Reliable system
- Before-save logic normalizes the automation state.
- The orchestrator validates, selects policy and delegates routing.
- A reusable fault subflow writes a correlation-based audit event.
- The scheduled path re-checks the Case before escalating.
Interactive system demo
Watch the system make the decision.
Choose a scenario, play the full path or inspect any decision directly. This is an explainable frontend model, not a live Salesforce connection.
Choose a path3 deterministic scenarios
Live system mapORCHESTRATION
Interactive frontend modelStep 1 / 6No live org connection
Architecture
Clear responsibilities. Explicit contracts.
01
Before-save Flow
Normalizes request data and initializes automation state without extra DML.
02
After-save orchestrator
Validates the Case, resolves SLA policy and calls the routing contract.
03
Invocable Apex
Returns one explicit routing result for each input Case.
04
Fault logging subflow
Captures correlation, source and recoverable context without re-entering Case automation.
05
Scheduled path
Re-queries business state before creating an escalation outcome.
Design decisions
Why the system is shaped this way.
Treat faults as process states
A failure gets a correlation ID, audit event and safe owner instead of becoming a silent technical detail.
Re-check delayed work
Scheduled escalation evaluates the current Case, not assumptions captured when it was created.
Production hardening
What changes before real users depend on it.
- Test create, update, reroute, resolved-before-SLA and recursion boundaries.
- Restrict field and object access for every automation user.
- Alert on terminal error states without exposing sensitive field values.
- Document recovery ownership and replay behavior.