Paths/Backend Engineer/Queues & Async Work / Failure Handling
Retry, Then Give Up
Transient failures deserve another attempt, real failures do not. Write the policy that decides which is which and where the exhausted messages go.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/backend/queues/retry-policy.yaml exists○
- The policy states the retry count and the backoff○
- The policy names the dead letter topic○
02Walkthrough
1 of 3 revealed- 01
Write the retry policy
max_retries with an exponential backoff - the wait grows so a struggling dependency gets room to recover.
echo 'retry_policy:\n max_retries: 5\n backoff: exponential\n initial_delay_seconds: 5\n max_delay_seconds: 300' > ~/backend/queues/retry-policy.yaml - 2 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list