Troubleshooting

Recover deliberately when setup, migration state, or documentation evidence does not agree.

Start from the failed boundary. Do not delete a database, rewrite a migration ledger, or create another mystery instance just because the first path is not understood.

The instance is unclaimed

Restore the developer happy path: owner, login, model key, and explicit instance identity.

A migration will not apply

Compare committed migration history with the database ledger before changing either.

The Server is degraded or unreachable

Identify the profile, topology, setup state, and failed boundary before changing anything.

An upgrade or restore failed

Preserve the recovery bundle and evidence, verify provenance, and recover deliberately.

Find another symptom

Search all public documentation and scenarios.

This page is a routing surface, not a claim that the troubleshooting corpus is complete.