LEVIATHAN ERROR CODES
A Leviathan code identifies the subsystem and failure class without hiding the original cause. Search the public catalog for likely causes, safe remediation steps and the diagnostic context that support may need.
CODE LOOKUP
Search by exact code, subsystem, symptom, HTTP status, technology or remediation term. Expand any result to see what to check next.
HOW TO READ A FAILURE
The user-visible code is designed to be searchable. The individual occurrence still keeps separate technical context so support can investigate without putting secrets into the code itself.
Example: LVT-DL-2004. The code identifies a reusable failure class and stays stable enough to search across the launcher, website, support and documentation.
A separate per-occurrence identifier connects one failure to privacy-safe logs, support records or incident history without changing the stable code.
HTTP status, Java exit code, XSTS XErr, stack trace, file error or native exception remains available when useful instead of being replaced by the Leviathan code.
Passwords, access tokens, refresh tokens, XSTS tokens, recovery codes and other credentials must never be embedded in a code, correlation ID or public diagnostic message.
If the catalog does not solve the problem, open a private support ticket and include the Leviathan code, correlation ID if shown, product version, platform and the preserved external error. The support form accepts the code directly so the case starts with useful context.
Public bug reports are appropriate for reproducible defects only when the report does not contain private account data or secrets.
