Domain 4 · 2.6% of the CCDV-F exam

Eval, Testing, and Debugging

Identify API errors and stop reasons, choose a recovery that matches the failure, read a trace, and separate an integration-layer bug from model output.

Task statements

4.1 · 2.6%
Debugging and Error Handling
Name the failure before you change the prompt. An HTTP error never reached a finished answer. A stop_reason tells you whether a successful response is complete, truncated, or waiting on a tool. The trace shows which of those happened, and which layer owns the fix.

Build exercises Quick reference

Build exercises

Split one failing turn into a layer

4.1 · Intermediate · 35 minutes

How an error body differs from stop_reason.
Which failures are safe to retry.
How a trace records tools and truncation.
When the fix belongs in the integration and when it belongs in the output.