docs: clarify which Prisma errors allow_requests_on_db_unavailable covers

[devin-ai-integration]

Summary

The "Gracefully handle DB unavailability" table in docs/proxy/prod.md said every Prisma error lets the request through. Since the auth fallback was narrowed to transient connectivity failures (is_database_connection_error allowlists httpx connection errors, EngineConnectionError and no_db_connection), query-level Prisma errors such as P2010 fail closed with a 401 because the database is reachable. A customer hit exactly that mismatch and asked what the intended blast radius is

This splits the row into "Prisma connection errors" (allowed, restricted INTERNAL_USER fallback identity) and "Prisma query errors" (blocked, 401), and adds a paragraph on what keeps working during an outage: cached virtual keys until user_api_key_cache_ttl expires, the master key and config-file models, while uncached key lookups, management endpoints and spend log writes wait for the database

Linear ticket

Resolves LIT-7857

Link to Devin session: https://app.devin.ai/sessions/62cc15985bf849119bbca4d1564b4a51
Open in Devin Desktop: https://app.devin.ai/desktop/session/62cc15985bf849119bbca4d1564b4a51?variant=devin

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[vercel]

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

Project	Deployment	Actions	Updated
litellm	Ready	Preview	Sep 16, 2026 10:28am UTC