Context Management & Reliability15% of the exam

Error propagation across multi-agent systems

How subagent failures should reach the coordinator: recover transient errors locally, propagate the rest with failure type, attempted query, partial results and alternatives, tell access failures from valid empty results, resume partial subagents, and annotate coverage gaps instead of suppressing errors or aborting the run.

Official exam objective
Implement error propagation strategies across multi-agent systems

~8 min read · 8 practice questions ·

What the exam expects

  • Return structured error context from a subagent (failure type, what was attempted, partial results, possible alternatives) instead of a generic "search unavailable".
  • Distinguish access failures (a timeout that needs a retry decision) from valid empty results (a successful query with no matches), and pick the coordinator action for each.
  • Recover transient failures inside the subagent and propagate only what it cannot resolve.
  • Reject both anti-patterns: silently returning empty results as success, and terminating the whole workflow on one failure.
  • Treat a subagent stopped by maxTurns as partial work to resume, and use structured status fields rather than scanning prose.
  • Annotate synthesis output with coverage: which findings are well supported and which topic areas have gaps because sources were unavailable.

Key terms: structured error context (machine-readable failure details a coordinator can act on); access failure (the source could not be reached or read); valid empty result (the query ran and found nothing); local recovery (bounded retries inside the subagent); partial result (completed work plus what is left); coverage annotation (per-topic statement of support and gaps).

Key facts

Structured error context
Detail
Failure type, attempted query, partial results, alternative approaches
Access failure vs valid empty
Detail
Timeout needs a retry decision; successful query with no matches is a finding
Both anti-patterns
Detail
Empty results reported as success; aborting the workflow on one failure
MCP tool execution errors
Detail
Returned in the result with isError: true; protocol errors are JSON-RPC errors
Recovery over restart
Detail
Resume from where the agent was; retry logic plus regular checkpoints
Subagent hits maxTurns
Detail
Output marked partial (Claude Code v2.1.246+); resume to continue
Resuming a subagent
Detail
Capture agentId and session ID; resume the session; history retained
API error ends a subagent
Detail
Never delivered as its result; background failures include last output
Foreground subagent cut off
Detail
Partial text returned with a note it didn't finish; no text means an error
SDK run outcome
Detail
ResultMessage.subtype; result only on success
Coverage annotations
Detail
Well-supported findings vs topic gaps from unavailable sources
Sources for this section (6)
  • Why is "search unavailable" a poor error report from a subagent?
  • When should a subagent handle a failure itself instead of propagating it?
  • Why resume a failed run rather than restart it?
  • What does Claude Code do with a subagent's output when it hits maxTurns?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Claude Certified Architect - Foundations pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 30 lessons of the Claude Certified Architect - Foundations guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Inline practice questions and one-click topic practice (8 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Claude Certified Architect - Foundations exam

Certifyforce is an independent study resource and is not affiliated with, endorsed by or sponsored by Anthropic. Claude is a trademark of Anthropic.