Troubleshoot apps

This topic describes how to fix common Snowflake App Runtime errors. To inspect an app’s state and logs first, see Quick troubleshooting runbook.

Deploy

Serverless compute isn’t enabled

If snow app deploy reports compute_resource SERVERLESS is not enabled for this account., run snow upgrade to update the Snowflake CLI, then deploy again. If the error persists, serverless compute isn’t enabled for the account. Contact your Snowflake representative.

Serverless deploy stops while the TLS certificate is issued

On the first serverless deploy in an account, the CLI checks for the TLS certificate that serverless endpoints share. If the certificate is missing, the CLI starts SYSTEM$ISSUE_PER_ACCOUNT_APP_SERVICE_CERTIFICATE automatically. A full deploy or snow app deploy --promote-only stops, but --upload-only and --build-only continue after a warning. Issuance can take up to three hours. Run the stopped command again after the certificate is ready.

If the CLI can’t check the certificate, such as when AWS PrivateLink, a proxy, or a custom certificate authority is in the path, the deploy continues without starting issuance. If the app URL later shows a browser warning, start issuance manually:

SELECT SYSTEM$ISSUE_PER_ACCOUNT_APP_SERVICE_CERTIFICATE();

Wait for issuance to finish, then run the deploy again.

Can’t upgrade or redeploy a disabled serverless app

You can’t upgrade, redeploy, or change the configuration of a disabled serverless app. Run ALTER APPLICATION SERVICE ... ENABLE, then try again. See Disable and enable a serverless app.

Sign-in and caller’s rights

Caller’s rights login fails on serverless compute

On serverless compute, the Sf-Context-Current-User-Token header holds the caller’s complete OAuth token. Authenticate with that token alone and authenticator: "OAUTH". A token joined with the session token, as managed compute requires, fails at login. Projects created with an older version of the snowflake-apps skill might join the tokens on every backend. See How you use the caller token depends on the.

Workspaces preview

Logs pane shows Container not ready

If the dev server isn’t running yet, for example right after you select Preview, the logs pane shows Container not ready and keeps checking. Wait for the dev server to start.

Preview stops restarting after crashes

If the dev server crashes three times in a row, each within 10 seconds of starting, Snowflake stops restarting it. To start it again, edit a source file, or select Shutdown and then reopen Preview.

Query results differ from the deployed app

A preview has no caller identity, so caller’s rights isn’t available. Apps from the Next.js App template run caller’s rights queries with the preview’s own credentials instead. Test row access and masking policies in a deployed app.

Next steps