troubleshooting · internal

The API runtime database identity was refused

The API could not prove that ordinary request traffic uses the restricted shoti_api_runtime identity against the same database as maintenance traffic. Production stays offline instead of falling back to the database owner.

fix

Provision the SQL-created shoti_api_runtime login, point SHOTI_RUNTIME_DATABASE_URL at the same host, port, and database as DATABASE_URL, then restart and require /health to report database_authority as restricted.

See also: migration-failure · migrate-direct-url

runtime-database-authority

Run shoti explain runtime-database-authority to read this offline. Still stuck? hello@shoti.ai.

All topics: shoti.ai/troubleshooting.