BerriAI/litellm · error · ProxyRateLimitError
Max iterations exceeded for session {session_id}. Current co
Error message
Max iterations exceeded for session {session_id}. Current count: {current_count}, max_iterations: {max_iterations}. What it means
Error "Max iterations exceeded for session {session_id}. Current count: {current_count}, max_iterations: {max_iterations}." thrown in BerriAI/litellm.
Source
Thrown at litellm/proxy/hooks/max_iterations_limiter.py:117
return None
max_iterations: Final = self._get_max_iterations(user_api_key_dict)
if max_iterations is None:
return None
verbose_proxy_logger.debug(
"MaxIterationsHandler: session_id=%s, max_iterations=%s",
session_id,
max_iterations,
)
# Increment and check
cache_key: Final = self._make_cache_key(session_id)
current_count: Final = await self._increment_and_get(cache_key)
if current_count > max_iterations:
resolved_model, llm_provider = resolve_llm_provider_for_rate_limit(data.get("model") if data else None)
raise ProxyRateLimitError(
detail=(
f"Max iterations exceeded for session {session_id}. "
f"Current count: {current_count}, max_iterations: {max_iterations}."
),
rate_limit_type=RateLimitType.MAX_ITERATIONS,
model=resolved_model,
llm_provider=llm_provider,
)
verbose_proxy_logger.debug(
"MaxIterationsHandler: session_id=%s, count=%s/%s",
session_id,
current_count,
max_iterations,
)
return None
View on GitHub (pinned to 77b7c6c40c)
Solutions
- Reduce the number of iterations in the agent loop for this session.
- Raise max_iterations in the limiter configuration if more iterations are expected.
When it happens
Trigger: Thrown at litellm/proxy/hooks/max_iterations_limiter.py:117 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/fc82bff71a26069c.
Report an issue: GitHub.