fix: add compact timeout cooldown evidence

This commit is contained in:
Codex
2026-06-10 07:42:21 +00:00
parent 9710a1a6f6
commit 8735b4103c
6 changed files with 85 additions and 14 deletions
@@ -28,7 +28,7 @@ pool:
durationMinutes: 10
description: Transient upstream server failures should start with a ten-minute cooldown and prefer another account.
- statusCode: 502
keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream, bad gateway, upstream request failed, websocket dial, handshake response, recovered upstream error]
keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream, bad gateway, upstream request failed, unknown error, context deadline exceeded, context canceled, websocket dial, handshake response, recovered upstream error]
durationMinutes: 30
description: Gateway upstream failures, including recovered upstream error wrappers, should cool down longer.
- statusCode: 413
@@ -44,7 +44,7 @@ pool:
durationMinutes: 30
description: Gateway timeout responses should cool down the selected account so another account can handle the next request.
- statusCode: 524
keywords: [timeout, a timeout occurred, cloudflare, gateway timeout, upstream, context deadline exceeded]
keywords: [timeout, a timeout occurred, cloudflare, gateway timeout, upstream, upstream request failed, unknown error, context deadline exceeded, context canceled, recovered upstream error]
durationMinutes: 30
description: Cloudflare 524 timeout responses should cool down the selected account so another account can handle the next request.
- statusCode: 529