Course 1.10 · Curriculum 2026.1
Debugging Flow when it fails silently
The worst flow failure is the one that reports success. Built around a screen flow that told field staff their time was logged while logging nothing, because 42 active orders had zero work orders and an empty collection loops zero times.
- Estimated effort
- 5 hr
- Lessons
- 42
- Modules
- 7
- Material
- 5 hr
Estimated effort is the sum of the lesson and lab times in this version of the course. It is not video runtime, which is lower.
Canadian dollars. One learner, lifetime access to this course version. Tax extra.
1 lesson free to preview
This course does not issue a certificate on its own. It counts toward the paths listed below, and those do.
01What you will learn
8 capabilities, stated as things you can do
Each one is what you should be able to do at the end, not what the course covers. If an outcome is not testable, it is not an outcome.
- Find the flow behind a symptom, starting from a record rather than from a list of flow names.
- Read a flow debug log and name the element that produced the wrong value.
- Detect the empty-collection path, where a loop runs zero times straight into a success screen.
- Add a stop screen and a minimum selection, so a flow cannot report work it did not do.
- Design fault paths that tell a person, rather than emailing an address nobody reads.
- Reproduce a user-reported failure under that user’s permissions rather than your own.
- Instrument a flow so the next silent failure leaves a record behind.
- Decide when a flow is past repair and has to be rebuilt.
02Curriculum
7 modules, 42 lessons
Every lesson shows its length and its type. A SCORM lesson looks like any other lesson, which is the point of ingesting packages rather than linking out to them.
7 modules · 42 lessons · 5 hr of material
A screen flow reported success while logging nothing. This module is the incident itself, told in full, before any fix.
- Video42 active orders, zero work orders, and a screen that said successThe activity flow listed an order’s work orders. 42 active orders had none. Field staff saw the empty list and the flow moved on anyway.Preview6 min
- VideoZero of zero items, Next, and Successfully Logged Field Activity7 min
- ReadingWhy an empty collection loops zero times straight into success6 min
- VideoThe cost of a failure nobody could see: what went unlogged7 min
- VideoSilence is not success: the rule this course is built around6 min
A symptom points at a record, not a flow name. This module is how to work backward from what a user saw to the automation that produced it.
- VideoStarting from a record, not a list of flow names6 min
- VideoFlow trigger explorer, and what actually fired on this record7 min
- ReadingNaming conventions that let you find a flow before you debug it6 min
- VideoWhen two flows could plausibly be the cause7 min
- VideoScheduled paths and platform events: the flows that do not show on the record6 min
- LabLab: find the exact flow responsible for a reported symptom7 min
The debug log names the element that produced the wrong value, if you know which lines to trust and which to skip.
- VideoTurning on debug logs without drowning in someone else’s6 min
- VideoReading a flow interview: elements, values, and where it diverged6 min
- ReadingThe debug log line that names the element that produced the wrong value7 min
- VideoDecision outcomes in the log, and the branch nobody expected to take6 min
- VideoAssignments and loops in the log, read in order7 min
- LabLab: read a debug log and name the element that broke6 min
The specific failure at the centre of this course, generalised: any loop over a collection that might be empty needs an explicit empty case.
- VideoDetecting the empty-collection path before it ships7 min
- VideoA Get element that returns nothing, and the loop that still runs6 min
- ReadingTesting a flow against the empty case on purpose6 min
- VideoCounting a collection before trusting what it implies7 min
- LabLab: reproduce the zero-work-orders case in a sandbox6 min
- VideoThe success screen that should have been conditional7 min
The actual fix: a stop screen, a minimum selection, and a fault path that reaches a person instead of an inbox nobody reads.
- VideoAdding a stop screen and a minimum selection6 min
- VideoDesigning fault paths that tell a person, not an inbox nobody reads7 min
- ReadingThe difference between a fault and an empty result, and why both need a path6 min
- VideoBack-dating so a missed day can be self-logged instead of invented6 min
- LabLab: add a stop screen and a fault path to a flow that had neither7 min
- VideoWriting the message a field user will actually read on a phone6 min
An admin cannot reproduce what an admin cannot see. Reproduce every reported failure under the reporting user’s own permissions.
- VideoReproducing a user-reported failure under that user’s permissions7 min
- VideoLogin As, and the permission difference an admin never sees6 min
- ReadingField-level security and record types: the two things that change per user6 min
- VideoBuilding the exact test data a reproduction needs, then deleting it7 min
- LabLab: reproduce a reported failure as the reporting user6 min
- VideoWhen the failure will not reproduce, and what that tells you7 min
The fix that outlasts this incident: build the flow so the next silent failure cannot stay silent.
- VideoInstrumenting a flow so a silent failure leaves a record behind6 min
- VideoA heartbeat object, and the alert that fires when nothing else does7 min
- ReadingDeciding when a flow is past repair and has to be rebuilt6 min
- VideoThe Apex equivalent of a stop screen, for the two fixes that needed it7 min
- LabLab: instrument a flow so its next failure cannot go silentThe capstone lab. Take a flow with a plausible empty-collection path and add the stop screen, fault path and instrumentation it is missing.29 min
- VideoVerifying the fix as the field user it was built for6 min
- QuizCheck: debugging flow14 min
03Before you start
What you need first
Assumed knowledge and setup
- Course 1.4. You should have shipped a record-triggered and a screen flow already.
- A Developer Edition org, and a second user you can log in as.
- No Apex, though the last module shows the Apex equivalent of two of the fixes.
Courses that come first
- 1.4 · Flow: the automation you will actually build8 hr · Intermediate
Part of these paths
- Salesforce AdministratorShareCo Certified Administrator
- The Full StackShareCo Certified Platform Engineer
04Who teaches it
Ege Taskent
Salesforce Developer, Certified Platform Administrator
The credential, and the rollout. The half of an implementation where people actually start using the thing.
Salesforce Certified Platform Administrator
05Reviews
No learner reviews yet
This course has not been taken by enough people to publish an honest rating, and we will not print invented quotes on a page that sells verification discipline. Here is what we can evidence instead.
- Assessment
- Lesson checks onlyThis course carries lesson checks. The certificate is issued by the path assessment, not by this course.
- Curriculum version
- 2026.1You enrol into a version. Content changes do not move you mid-course, and your required-lesson count is snapshotted at enrollment.
- Refunds
- 14 daysFull refund within 14 days if you have completed under a quarter of the required lessons. Stated here rather than in a footer.
Start 1.10
Enrol as an individual, or buy seats and assign this course to your team. Progress is reported per lesson, per module and per path.
- 5 hr estimated effort, labs included
- Lifetime access to the version you enrol in
- A ShareCo certificate is not a Salesforce certification