Triage a failing browser run

Incident The browser run stopped at record 83 of 140. The page shows no obvious error, but the agent log says the expected Save button was not found. Your next move determines whether you create duplicate side effects or recover cleanly. Five Whys under pressure Evidence -> expectation -> cause -> controlled action Start from what is observable, then ask why the expected condition was missing. Do not rerun or patch until you know whether the previous action created a side effect. Reflex Rerun the whole batch Recovery without duplicate actions. Treat every failed browser run as partially completed until…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in