BerriAI/litellm · error · Exception
Error updating version status: {e}
Error message
Error updating version status: {e} What it means
DB error wrapper in the policy registry: updating the version_status row (including the production demotion dance and in-memory refresh) raised; the exception is logged and re-raised with this prefix.
Source
Thrown at litellm/proxy/policy_engine/policy_registry.py:960
policy: Final = self._parse_policy(
policy_name,
{
"inherit": updated.inherit,
"description": updated.description,
"guardrails": {
"add": updated.guardrails_add or [],
"remove": updated.guardrails_remove or [],
},
"condition": updated.condition,
"pipeline": updated.pipeline,
},
)
self.add_policy(policy_name, policy)
return _row_to_policy_db_response(updated)
except Exception as e:
verbose_proxy_logger.exception("Error updating version status: %s", e)
raise Exception(f"Error updating version status: {e}")
async def compare_versions(
self,
policy_id_a: str,
policy_id_b: str,
prisma_client: "PrismaClient",
) -> PolicyVersionCompareResponse:
"""
Compare two policy versions and return field-by-field diffs.
Args:
policy_id_a: First policy version ID
policy_id_b: Second policy version ID
prisma_client: The Prisma client instance
Returns:
PolicyVersionCompareResponse with both versions and field_diffs
"""View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check DB connectivity and the error detail; retry the status transition.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/policy_engine/policy_registry.py:960 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/e5d2ee0601a40b09.
Report an issue: GitHub.