Portal

Refusal codes

Each refusal carries a code. This list is the full set. How to read a refusal is explained in Refusals.

Code Severity Means Fix
secret_in_client_bundle warn A secret in code the browser downloads Move the call to the server, set the key as a secret, rotate it
secret_in_source warn A secret key or working credential in your code Read it from the environment, set it as a secret, rotate it
secret_in_sample warn Something key-shaped in an example, test or docs file Check it is a placeholder
secret_scan note The scanners found what may be secrets; Kaviris does not block for them Check the list; your secrets are your responsibility
publishable_key note A key meant to be public Supabase: turn on row-level security
vuln_fixable advise A dependency with a known hole and a fixed version Apply the ready-made upgrade patch, commit, deploy
vuln_unfixable advise A dependency with a known hole and no fix yet None yet; checked nightly
code_pattern warn A risky code pattern Change the code at the line named
data_without_disk warn The app keeps data in files and has no disk, so they are lost on every sleep Add a disk ("Add a disk"), then approve
egress_undeclared needs approval The app tried to reach a host the contract doesn't name Add the host and approve, or remove the call
port_undeclared needs approval / refuse The app listens on another port, or on a second one Listen on the contract's port, or change it
port_mismatch needs approval The app runs but listens on another port, usually one written into the code Listen on PORT, or change the contract's port
approval_expired refuse A deploy waited 24 h for approval Approve, then deploy again
build_failed error The source did not build Read the build log and fix
build_timeout error The build ran past its 30 minutes Make the build exit; read the build log
start_failed error The app did not answer on its port within 4 minutes Listen on the contract's port, set required secrets
release_failed error The release step (migrations, once per deploy) failed; the previous version keeps serving Run the release command locally against a copy of your database and fix it
platform_error error Something failed on our side Deploy again
quota_exceeded refuse Your plan's limit on apps or deploys a day is reached Delete an app, wait, or ask for a bigger plan
not_admitted refuse Your account is still waiting to be let into the beta Wait for the email
app_stopped refuse The app is stopped: no owner or admin of the organisation was active for 30 days An owner or admin presses "Put my app back" (agents: resume_app)
name_quarantined refuse The name belonged to an app that was deleted or renamed and is still held Pick another name, or wait for the date given
account_deleting refuse The account is locked because its deletion was asked for Sign in and press Reactivate before the date (signing in alone does not)
last_owner refuse You are the last active owner of an organisation others are in Have support transfer it, or delete the organisation
personal_org refuse A personal organisation takes no invitations and is not deleted on its own Create a team organisation; delete the account instead
legal_hold refuse The app or organisation is retained under a legal obligation Contact support

Severities

Severity Effect
refuse The deploy stops. The running version stays
needs_approval The deploy waits until the contract change is approved, then continues without rebuilding
error The build or the start failed
advise A recommendation with a ready-made fix, such as an upgrade for a vulnerable library. The deploy goes on
warn, note Information. The deploy goes on

Codes you may see later

These are reserved and not used yet: datastore_undeclared (the app needs a database its contract doesn't have), unsupported_shape (a kind of app Kaviris can't run yet) and plan_required (a feature your plan doesn't include).

When organisation policies arrive, an organisation's own rules will add refusals of their own.

This page as Markdown