BerriAI/litellm · error · GuardrailRaisedException

Blocked by Singulr: {result.blocking_due_to or 'unknown'}

Error message

Blocked by Singulr: {result.blocking_due_to or 'unknown'}

What it means

Error "Blocked by Singulr: {result.blocking_due_to or 'unknown'}" thrown in BerriAI/litellm.

Source

Thrown at litellm/proxy/guardrails/guardrail_hooks/singulr/singulr.py:211

        input_type: str,
        logging_obj: "LiteLLMLoggingObj | None" = None,
    ) -> GenericGuardrailAPIInputs:
        payload: Final = self._build_payload(request_data, inputs, input_type)
        if not payload:
            return inputs

        result: Final = await self._call_api(payload)
        if result is None:
            return inputs

        verbose_proxy_logger.debug(
            "Singulr: should_block=%s blocking_due_to=%s",
            result.should_block,
            result.blocking_due_to,
        )

        if result.should_block:
            raise GuardrailRaisedException(
                guardrail_name=self.guardrail_name,
                message=f"Blocked by Singulr: {result.blocking_due_to or 'unknown'}",
            )

        return inputs

View on GitHub (pinned to 77b7c6c40c)

Solutions

1. Review the blocking_due_to reason and modify the request content.
2. Adjust the Singulr guardrail policy if the block is a false positive.

When it happens

Trigger: Thrown at litellm/proxy/guardrails/guardrail_hooks/singulr/singulr.py:211 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/fc65f86143d0afe1. Report an issue: GitHub.