OctaFuse 2.1.1: identifiable errors and more precise circuits
Published
OctaFuse Gateway 2.1.1 is now available.
This release strengthens production reliability by aligning circuit state, Failover decisions, error responses, and diagnostics under one contract.
Unified user + model circuits
Section titled “Unified user + model circuits”Sensitive-content failures and ordinary upstream 400 responses now share one user+model backoff sequence:
20 seconds → 1 minute → 3 minutes → 5 minutes → 10 minutesShort-circuit responses still identify the reason with circuit.sensitive_content or circuit.client_error. Images and Audio no longer enter ordinary client-error circuits, because malformed media requests should not block later valid calls; sensitive-content circuits remain active.
Failover checks current Provider state
Section titled “Failover checks current Provider state”The Failover loop now rechecks a Provider’s circuit before each attempt, so an upstream that just entered cooldown is not called again in the same dispatch. Authentication-related 401 / 403 cooldown changes from ten minutes to five, retaining protection from repeated invalid credentials while recovering sooner from temporary auth problems.
Stable error codes
Section titled “Stable error codes”Gateway-generated, circuit, and classified upstream errors gain a fixed code plus the response header:
X-OctaFuse-Error-Code: circuit.client_errorCodes are grouped under gateway.*, circuit.*, and upstream.*. The existing error body shape remains compatible, while clients can stop parsing human-readable messages to make control-flow decisions.
gateway.upstream_request_failed also includes a truncated summary of the original fetch failure, improving diagnosis in client logs and external observability systems.
Catalog updates
Section titled “Catalog updates”Admin adds the production qwen3.8-max and qwen3.7-flash presets, corrects qwen3.8-max-preview, and aligns the token limits of qwen3.7-plus and qwen3.7-max to 128000.
No database migration or configuration change is required.
Learn more about OctaFuse or explore the source:
If OctaFuse is useful to your project, consider giving the repository a Star. Your interest and feedback help us keep improving gateway reliability and observability.