Instruction: Explain how you would stop duplicate side effects across integrated systems.
Context: Tests how the candidate diagnoses the problem, chooses the safest next step, and reasons through recovery. Explain how you would stop duplicate side effects across integrated systems.
Official answer available
Preview the opening of the answer, then unlock the full walkthrough.
I would add idempotency keys, explicit action status tracking, and confirmation checks before retry. If the model or orchestrator cannot tell whether the prior action already committed, retries are dangerous by default.
I also want the recovery policy outside the model where...
easy
easy
easy
easy
easy
easy