internal_error

Docs version v1 (main) · Nauthera is pre-1.0, in a design-partner program

The server accepted the operation and could not complete it (500).

#Meaning

The work was attempted and failed, and the outcome must not be treated as achieved. Examples: a sign-out whose session could not be revoked ("you are still signed in"), a consent decision or logout confirmation that could not be stored, an organization that could not be built for serving, or an admin token check that could not be completed. Other server faults are a 500 with no code.

#Impact

The user or administrator is told the action did not happen. For a sign-out, the session stays valid. It is not expected in normal operation and points at a store or dependency failure.

#Diagnosis

1. Search the logs for the request id; the log line carries the error, which the response never does.
2. On the Troubleshooting page the record is filed with reason internal_error, or unavailable with a stage when a store did not answer.
3. Check database and cache health and recent deploys.

#Mitigation

• As a user: try again; for a sign-out, try again before leaving a shared device.
• As a client developer: retry once, then show an error; do not assume success.
• As an operator: restore the failing dependency named in the log.

#Escalation

Escalate when it repeats with healthy dependencies. Open an issue with the request id, the log lines for it (redacted of addresses and secrets) and the server version.

Problem code runbooks · Generated from internal/runbook/problems.yaml in nauthera-server.