Paths/Data Engineer/Orchestration & Scheduling / Reliability & Recovery
Set Retry and Backoff Policies
Transient failures are normal - a network hiccup is not a broken pipeline. Write the policy that says when to try again and when to give up.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/orchestration/policies.yaml exists○
- The policy states how many retries a task gets○
- The policy states the backoff between attempts○
- The policy states the deadline for a single task○
02Walkthrough
1 of 4 revealed- 01
Write the retry policy
max_retries is how many times a transient failure gets another go. Three is usually enough - more just delays the alert.
echo 'policies:\n default:\n max_retries: 3\n backoff_seconds: 60\n timeout_seconds: 3600' > ~/orchestration/policies.yaml - 3 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