Count wire attempts and durable retries separately.Body size answers what was sent; it does not answer how many times.
Join four timelines.
Each step rebuilds model-facing surface messages.
Every visible retry records delay and identity.
Trace cancellation through both proxy directions.
One visible retry owner.
pi-ai SDK retries
default transient retries
in-cap Retry-After delay
signal + iterator teardown
Do not use always mode to diagnose overload.
It can retry permanent failures without a request limit.
Use the complete incident runbook.
The canonical guide covers request reconstruction, retry ownership, Retry-After, cancellation, gateway evidence, request-size controls, and a publish-safe checklist.
Read the complete guide