fix: 按严重程度设置 Sub2API 错误冷却

This commit is contained in:
Codex
2026-06-09 10:27:20 +00:00
parent 7dd7b893ed
commit 1120ed286e
4 changed files with 22 additions and 22 deletions
+10 -10
View File
@@ -19,24 +19,24 @@ pool:
description: Permission, quota, or account-state failures should fail over to another account for at least two hours.
- statusCode: 429
keywords: [capacity, rate limit, rate_limit, quota, too many requests, overloaded, resource_exhausted]
durationMinutes: 120
description: Capacity and rate-limit responses should cool down this account for at least two hours and use another account.
durationMinutes: 10
description: Capacity and rate-limit responses are often temporary; start with a ten-minute cooldown and use another account.
- statusCode: 500
keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream]
durationMinutes: 120
description: Transient upstream server failures should prefer another account for at least two hours.
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]
durationMinutes: 120
description: Gateway upstream failures should prefer another account for at least two hours.
durationMinutes: 30
description: Gateway upstream failures are more disruptive than transient capacity signals and should cool down longer.
- statusCode: 503
keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream]
durationMinutes: 120
description: Service unavailable responses should prefer another account for at least two hours.
durationMinutes: 30
description: Service unavailable responses should cool down longer than one-off transient failures.
- statusCode: 529
keywords: [capacity, overloaded, temporarily unavailable, temporary]
durationMinutes: 120
description: Provider overloaded responses should cool down this account for at least two hours and use another account.
durationMinutes: 30
description: Provider overloaded responses should cool down longer than generic transient failures and use another account.
profiles:
entries:
- profile: default