Documentation Index
Fetch the complete documentation index at: https://docs.lasscyber.com/llms.txt
Use this file to discover all available pages before exploring further.
| HTTP status | 503 Service Unavailable |
| Code | analyzer_unavailable |
| Retry? | Yes — honour Retry-After. SDKs retry automatically with backoff. |
When this happens
A specific upstream that one of the analyzers depends on is degraded or temporarily unavailable. The detail object names which analyzer failed and the upstream HTTP status (when known). Examples:- The internal model service is unreachable (prompt-injection classifier or ShieldGemma).
- Google Cloud DLP, NLP, Web Risk, or Vertex AI Embeddings is in a partial outage.
Example response
How to recover
- Read
Retry-After(seconds). - Sleep + jitter, then retry up to 3 times.
- If the third attempt still fails, escalate to the status page.
ServerError (Python) / ServerError (TypeScript) only after the
configured retry budget is exhausted.
Failing open vs closed
Agnes intentionally fails closed onanalyzer_unavailable so
production traffic does not silently skip an analyzer the policy
relies on. If your application needs to fail-open during analyzer
outages (a deliberate choice — most do not), catch the SDK exception
and degrade gracefully:
SDK behaviour
| SDK | Exception |
|---|---|
| Python | agnes.ServerError (with code == "analyzer_unavailable") |
| TypeScript | ServerError (with code === "analyzer_unavailable") |
Related
service_unavailable— generic 503 not tied to a specific analyzer.- Combined analyzer — which analyzers call which upstreams.
- status.lasscyber.com — public health / incident history.