Inference requests and APIs · Lesson 8 of 16 · 5 min

Review retry boundaries

Retry policies need a maximum attempt count, delay and retryable failure set. Unbounded retries can amplify overload and duplicate work.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read the case evidence
Read /opt/ai-lab/cases/aiops-inference-apis-008.json. Separate the recorded facts from your assumptions.
Hint & worked example
Retry policies need a maximum attempt count, delay and retryable failure set. Unbounded retries can amplify overload and duplicate work.
The complete case JSON is read successfully.
```
cat /opt/ai-lab/cases/aiops-inference-apis-008.json
```
Common mistake to avoid: Keep retrying indefinitely whenever the status is 503.
2
Isolate the deciding signal
Select the attempts_used field from the case JSON. What does it establish—and what does it not establish?
Hint & worked example
Stop automatic retries because this request has exhausted its three-attempt budget.
A successful JSON query isolates attempts_used.
```
jq .attempts_used /opt/ai-lab/cases/aiops-inference-apis-008.json
```
Common mistake to avoid: Using a different case or an unrelated signal as the justification.
3
Record your operational decision
Choose the justified code: stop-retry-budget, change-without-evidence, or ignore-the-signal. Save that one code followed by a newline in /home/learner/lab/aiops-inference-apis-008-decision.txt.
Hint & worked example
Stop automatic retries because this request has exhausted its three-attempt budget.
The decision artifact contains the correct code, not just a matching command in history.
```
printf '%s\n' 'stop-retry-budget' > /home/learner/lab/aiops-inference-apis-008-decision.txt
```
Common mistake to avoid: Keep retrying indefinitely whenever the status is 503.

Understand the pattern

Retry policies need a maximum attempt count, delay and retryable failure set. Unbounded retries can amplify overload and duplicate work.

Interpret the evidence

Stop automatic retries because this request has exhausted its three-attempt budget.

A tempting mistake

Keep retrying indefinitely whenever the status is 503.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result

$ cat /opt/ai-lab/cases/aiops-inference-apis-008.json

{
  "fixture": "Fictional training data; not a live measurement.",
  "status": 503,
  "retryable": true,
  "attempts_used": 3,
  "max_attempts": 3
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .attempts_used /opt/ai-lab/cases/aiops-inference-apis-008.json

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'stop-retry-budget' > /home/learner/lab/aiops-inference-apis-008-decision.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “stop-retry-budget” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Review retry boundaries” justify?Stop automatic retries because this request has exhausted its three-attempt budget.Keep retrying indefinitely whenever the status is 503.Make the change now and gather the missing evidence afterward.

Apply it elsewhere

A colleague concludes: “Keep retrying indefinitely whenever the status is 503.” What should you do?Accept it because the training command completed.Treat this fixture as a live measurement.Reject that conclusion; return to the case evidence and its stated limits.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Inspect a request identifier Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

Case methodology: evidence, limits, decision