Synthetic example: choose a recovery policy before changing a background worker. Replace this content when creating a real artifact.
Choose one recovery policy and any constraints that should shape it.
Copy the result back to your coding agent.
This finding is illustrative. Replace it with a verified file reference in a real review.
“A network timeout does not prove that the provider rejected the request.”
A wrong answer points to an explanation. Passing this check never grants permission to deploy or spend.
Keep the first read short without hiding material constraints.
The provider may have accepted the request before the connection failed. Retrying blindly may duplicate work or charges.
Look up the provider request ID or other durable evidence, record the actual outcome, then decide whether a new request is needed.
Only cards with a category participate in filtering.
The worker records a timeout but may already have sent the provider request.
The example request has no stable idempotency key yet.
Choose automatic idempotent retry or manual reconciliation.
Set a maximum charge before any retry policy is enabled.