How did you handle retries?
Practice this questionDiscussion template: use your own project facts, ownership, and measured outcomes. Bracketed text is a placeholder.
Short explanation:
A retry policy decides which failures may be attempted again, how long to wait and when to stop. It is valuable for temporary faults but dangerous for non-idempotent side effects. Explain the actual policy and duplicate protection used, or clearly say that a policy was missing.
Key points:
-
Describe the actual retry trigger, limit and delay.
-
If it was not implemented, say so; a proposed improvement is backoff with safe duplicate handling.
-
Include what happened after retry exhaustion and how an operator could inspect or replay the failed work.
Interview point:
- Distinguish a definite rejection from a timeout with an unknown external outcome.
Adapted from 10_RESUME_PROJECT_DEEP_DIVE.md · “How did you handle retries?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.