mirror of
https://github.com/BerriAI/litellm.git
synced 2026-08-28 05:25:59 +00:00
commit
5c1f7d99bf
2 changed files with 4 additions and 0 deletions
BIN
docs/my-website/img/release_notes/guardrail_fallbacks.png
Normal file
BIN
docs/my-website/img/release_notes/guardrail_fallbacks.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 435 KiB |
|
|
@ -71,8 +71,12 @@ The Skills Marketplace gives teams a self-hosted catalog for discovering, instal
|
|||
|
||||
### Guardrail Fallbacks
|
||||
|
||||

|
||||
|
||||
Guardrail pipelines now support an optional `on_error` behavior. When a guardrail check fails or errors out, you can configure the pipeline to fall back gracefully — logging the failure and continuing the request — instead of returning a hard 500 to the caller. This is especially useful for non-critical guardrails where availability matters more than enforcement.
|
||||
|
||||
[Get Started](../../docs/proxy/guardrails/policy_flow_builder)
|
||||
|
||||
### Team Bring Your Own Guardrails
|
||||
|
||||
Teams can now attach guardrails directly from the team management UI. Admins configure available guardrails at the project or proxy level, and individual teams select which ones apply to their traffic — no config file changes or proxy restarts needed. This also ships with project-level guardrail support in the project create/edit flows.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue