Design an agent that can resume after partial failure without repeating side effects.
Instruction: Describe how you would let an agent resume safely after interruption or partial completion. A payment-related side effect is pending in a checkpoint. Its last dispatch was 27 hours ago; the provider deduplicates keys for 24 hours and has no definitive operation lookup. No record proves whether it committed. May restart simply reuse the key?
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
I would resume from the last durable checkpoint, but first reconcile any operation that was in flight when the failure occurred. A recorded pending step is not proof that its external side effect never happened...
Your preparation path
Work through these questions in order. Read the answer aloud, then explain it in your own words.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- Design an agent that can resume after partial failure without repeating side effects. Member answer
- After a model upgrade, how would you decide which agent-harness rules to remove? Member answer
- An agent's execution container dies halfway through a task. What survives, and how does it recover? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy