Expose HTTP transient retry control and preserve shared capacity
This commit is contained in:
@@ -143,7 +143,7 @@ rendering continues to work. No application-owned retry/backoff loop exists.
|
||||
|
||||
## Stage 3: Expose HTTP Retry Control And Verify Shared Admission
|
||||
|
||||
**Status: Pending.**
|
||||
**Status: Complete.**
|
||||
|
||||
Selected interface: optional top-level JSON `transient_retries` integer on
|
||||
`POST /v1/runs`; omission/null inherits the engine, zero disables additional
|
||||
|
||||
Reference in New Issue
Block a user