internal_error


HTTP status	`500 Internal Server Error`
Code	`internal_error`
Retry?	Optional — single retry is fine; quote `request_id` when reporting.

When this happens

The server hit an unexpected failure that it could not categorise as validation_error, one of the analyzer- or service-level 503 errors, or anything else specific. Operators are paged automatically.

Example response

The API never includes stack traces or upstream error strings in 500 bodies — only the canonical envelope:

{
  "detail": "An unexpected error occurred.",
  "code": "internal_error",
  "request_id": "5b3f6c7e-7d24-4d40-9b12-3a59c01c6e91",
  "doc_url": "https://docs.lasscyber.com/errors/internal_error"
}

What to do

Optionally retry once. Some 500s are genuinely transient.
If the retry also fails, file a support ticket from agnes.lasscyber.com/support and quote the request_id. The team uses it to correlate the exact server-side log line.
Check the status page — if a broader incident is open, the resolution there will fix the call.

SDK behaviour

SDK	Exception
Python	`agnes.ServerError`
TypeScript	`ServerError`

SDKs retry 5xx errors up to the configured budget. A surfaced ServerError with code: "internal_error" means retries were exhausted.

Privacy

500 responses never echo customer prompts back, never include upstream credentials, and never include database identifiers. The request_id is the only identifier you need to quote in a ticket; do not paste prompts.

service_unavailable — retryable 503.
analyzer_unavailable — analyzer- specific 503.
status.lasscyber.com

Reference

Errors

internal_error

When this happens

Example response

What to do

SDK behaviour

Privacy

​When this happens

​Example response

​What to do

​SDK behaviour

​Privacy

​Related

When this happens

Example response

What to do

SDK behaviour

Privacy

Related