docs(proxy): document fail_closed_budget_enforcement

[yassin-berriai]

Summary

Documents the new general_settings.fail_closed_budget_enforcement flag added in the proxy PR (BerriAI/litellm#30684), which makes budget enforcement validate spend against the authoritative database for every budgeted request and reject with a 503 when spend cannot be verified against Redis or the database.

Changes

docs/proxy/config_settings.md: adds fail_closed_budget_enforcement to the general_settings YAML example and the reference table.

docs/proxy/users.md: adds a "Hard budget enforcement (fail closed)" section under Budgets explaining when to use the flag, what it covers (key, team, user, organization, end-user, tag, and per-window budgets), the bounded database cost, the 503-on-unverifiable behavior, and the default behavior when the flag is off.

Related

Proxy change: BerriAI/litellm#30684

---

Note

Low Risk
Documentation-only changes with no runtime or config parsing impact in this PR.

Overview
Documents general_settings.fail_closed_budget_enforcement for the proxy behavior introduced in BerriAI/litellm#30684.

docs/proxy/config_settings.md adds the flag to the general_settings YAML example and the reference table (default false, per-request DB validation when true, 503 when spend cannot be verified via Redis or DB, link to the users guide).

docs/proxy/users.md adds Hard budget enforcement (fail closed) under budgets: Redis hot-path vs DB authority after Redis restarts, scope (key/team/user/org/end-user/tag/per-window budgets), coalesced in-process DB reads, and how default mode differs (no per-request DB read; cross-check when Redis is below last-known spend).

^{Reviewed by Cursor Bugbot for commit a25b794. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Jun 18, 2026 4:59pm

[mateo-berri]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit a25b794. Configure here.}