BerriAI/litellm · error · HTTPException

Error checking session status: {e}

Error message

Error checking session status: {e}

What it means

Error "Error checking session status: {e}" thrown in BerriAI/litellm.

Source

Thrown at litellm/proxy/management_endpoints/ui_sso.py:2536

                "user_id": user_id,
                "team_id": team_id,
                "teams": user_teams,
                # Echo back any team details we have so clients can
                # present nicer information if needed.
                "team_details": user_team_details,
            }
            attribution_metadata = _cli_poll_attribution_metadata_from_session(session_data)
            if attribution_metadata:
                poll_response["attribution_metadata"] = attribution_metadata
            return poll_response
        else:
            return {"status": "pending"}

    except HTTPException:
        raise
    except Exception as e:
        verbose_proxy_logger.error("Error polling for CLI JWT: %s", e)
        raise HTTPException(status_code=500, detail=f"Error checking session status: {e}")


async def insert_sso_user(
    result_openid: OpenID | dict | None,
    user_defined_values: SSOUserDefinedValues | None = None,
) -> NewUserResponse:
    """
    Helper function to create a New User in LiteLLM DB after a successful SSO login

    Args:
        result_openid (OpenID): User information in OpenID format if the login was successful.
        user_defined_values (Optional[SSOUserDefinedValues], optional): LiteLLM SSOValues / fields that were read

    Returns:
        Tuple[str, str]: User ID and User Role
    """
    verbose_proxy_logger.debug("Inserting SSO user into DB. User values: %s", user_defined_values)
    if result_openid is None:

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Check the embedded error and proxy logs, then retry the session status request.

When it happens

Trigger: Thrown at litellm/proxy/management_endpoints/ui_sso.py:2536 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/e5fc0be54e895298. Report an issue: GitHub.