A 500 is a symptom.
Not retry permission.
Review one failed API request against method semantics, business side effects, operation state and documented idempotency. Ambiguous writes are held for source-system or human confirmation; this page never replays traffic.
Single-request retry evidence check
Why this is held or conditional
Required human/source checks
“Conditional review candidate” is not an automated retry instruction. Verify the current provider/internal contract, attempts, pacing and authoritative resource state.
Reliability boundary: this tool never calls an endpoint, replays a request, changes traffic, approves a write, or guarantees safety. HTTP method and status semantics do not prove an implementation's business behavior. Unknown and partial write outcomes require source-system or human confirmation.
$49/mo Retry Policy Registry
Turn the current review into a team-owned policy row, change-review checklist, exception approval and incident evidence record. The first release is read-only; automatic retries, replays and traffic switching stay outside the product.
- Endpoint retry-policy registry row
- Unknown/partial-result investigation checklist
- Idempotency, pacing and max-attempt evidence gates
- Policy change, exception and incident approval record
Protocol semantics and visible retry substitutes
先核对当前来源与工具边界Check current sources and tool limits first