Add review, errors, and recovery
Want more background?
The idea in everyday life
Make failures visible, route uncertain work to a person, and prevent retries from creating damage.
A reliable automation fails loudly, safely, and reversibly.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Restore the exported run and enable its trigger. Change only T06 destination_available to yes, then rerun the six cases without resetting the queue.
- 2
Expect DUPLICATE, DUPLICATE, DUPLICATE, REVIEW, SKIPPED, CREATED, with 3 destination rows and 12 cumulative log entries. Historical review items and alerts stay visible as evidence.
- 3
The fixture owner confirms B104 belongs in Room B. Correct T04, replay only that header/row and verify B104 appears once; replay again to prove duplicate protection. Record the approval source.
- 4
Write the owner guide from README: pause, export, restore matching release/config, inspect each batch, correct from confirmed source, replay stable IDs, use manual fallback and preserve rollback evidence.
See how it works.
Outage recovery creates B106 only after the destination is available. Existing B101/B102 never duplicate. Approved correction of B104 yields Room B, 30 minutes, Ari. The review queue does not approve itself; old alerts are historical records, not an unresolved-case count.
Did you cover these?
- Your work includes an exception design with approval rules, duplicate protection, alerts, recovery procedure, and fallback owner.
- Check this common mistake: Sending every failure to a generic inbox without enough context or ownership to resolve it.
- A simulated outage and duplicate trigger produce a visible, owned, reversible response without double-processing.
What to finish
An exception design with approval rules, duplicate protection, alerts, recovery procedure, and fallback owner.
Watch for this
Sending every failure to a generic inbox without enough context or ownership to resolve it.
How can I tell I understand it?
A simulated outage and duplicate trigger produce a visible, owned, reversible response without double-processing.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
Power Automate Tutorials
From Microsoft Power Automate. Watch here or open it on YouTube .
Watch for an idea you can use in the practice below. You can pause or skip this optional overview.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.