The agent recovers from errors, but leaves partial side effects in downstream systems. How would you fix it?

Instruction: Explain how you would handle partial writes and repeated actions in an agent workflow.

Context: Tests how the candidate diagnoses the problem, chooses the safest next step, and reasons through recovery. Explain how you would handle partial writes and repeated actions in an agent workflow.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would redesign the workflow around idempotency and compensating actions. If the agent can partially succeed and then retry or continue, the downstream systems need a way to recognize duplicate intent and either ignore repeats or roll back safely.

I also want the orchestrator to track...

Related Questions