Deployments
A failed deployment carries anerror_code and an error_message. See Why a deploy fails.
| Code or message | Means | Fix |
|---|---|---|
invalid_config | A readiness check failed before the build | Readiness checks |
build_failed, BUILD_TIMEOUT | The Docker build failed or ran out of time | Build logs |
deploy_failed, Release command failed: | The release command or the new revision failed | Why a deploy fails |
The container did not start listening on port, The container exited before it started listening on port | The app crashed at boot or listens on the wrong port | Container port, When the app crashes at boot |
healthcheck_failed | Cloud Run didn’t report the new revision ready, and the health check path didn’t answer 200 | Health checks and traffic |
permission_denied, Deployment is unavailable because | Plan, trial, suspension or hosting hold | Why a deploy fails |
timeout | A step stalled and was stopped | Deploy again |
One or more configured secrets are missing or unavailable | A secret the environment needs is gone | Environment variables |
Your migration ... creates the Session table together with other tables | prisma migrate deploy would fail with P3005 | Why a deploy fails |
Dockerfile not found at root of repository, DOCKERFILE_MISSING | No Dockerfile at the repository root | What your repository needs |
ENVIRONMENT_NOT_READY | The environment’s database is still being created | The first deploy waits for the database |
A deployment is already in progress for this environment | One deployment at a time per environment | Follow it, then deploy again |
Readiness checks
Returned bymeridian doctor, app_readiness_get and a deploy’s own checks, as each check’s code. All are explained in Readiness checks.
| Code | Means |
|---|---|
missing_shopify_client_id, missing_shopify_client_secret | The Shopify credentials are not saved on the Meridian SDK page |
shopify_partner_not_connected, missing_shopify_app_id | The Shopify Partner connection is missing or incomplete |
shopify_partner_token_rejected, shopify_partner_ids_not_found, shopify_partner_unreachable, shopify_partner_connection_error | The last Shopify Partner connection attempt failed: Shopify refused the token, found no organization or app with that ID, or could not be reached. The last code means another failure, shown on the Shopify card in App settings > Integrations |
repository_not_connected, missing_dockerfile | No repository, or no Dockerfile at its root |
auto_deploy_production_branch_unprotected | Pushes deploy to production from a branch GitHub or GitLab reports as unprotected |
database_provisioning, database_failed | The environment’s database is not ready |
database_missing_for_prisma | The repository has Prisma migrations and the environment has no database |
sqlite_provider, local_file_url | Prisma doesn’t point at the attached database |
prisma_migrations_without_release_command | Migrations exist but nothing runs them |
missing_shopify_app_url, shopify_app_url_custom_domain, shopify_app_url_mismatch | SHOPIFY_APP_URL is missing, points at the wrong address, or isn’t application_url in shopify.app.toml |
scopes_mismatch | A SCOPES you set doesn’t match shopify.app.toml |
no_active_plans | Plan Builder has no active plan |
custom_domain_not_ready | A custom domain is not active yet |
datasource_not_database_url, session_model_missing, missing_shopify_app_toml, missing_application_url | Only from meridian doctor in a repository not linked to an app: the Prisma datasource ignores DATABASE_URL, the schema has no Session model, or shopify.app.toml or its application_url is missing. See Doctor before the app exists |
Plans and billing
| Code or message | Means | Fix |
|---|---|---|
SHOPIFY_BILLING_NOT_READY | The app can’t charge through Shopify yet | Paid plans need Shopify billing set up, Shopify billing is not set up |
PLAN_BUILDER_UNAVAILABLE | Meridian can’t read the app’s Shopify session store | What the session store can block |
PLAN_LOCKED | Subscribers would pay more: save a new version | Meridian MCP troubleshooting |
PLAN_NOT_LATEST_VERSION | A newer version of the plan exists | Meridian MCP troubleshooting |
PLAN_VALIDATION_ERROR | The plan breaks a rule the message names | Meridian MCP troubleshooting |
USAGE_VIEW_PLAN_LOCKED | A plan prices a view of this event | Meridian MCP troubleshooting |
Plan not found on subscribe | planId is a handle or an old version | useMeridian actions |
Meridian MCP
| Message | Means | Fix |
|---|---|---|
App not found, or you do not have access to it. | Wrong app_id, or a permission your role lacks | Plan requirements |
This app's Meridian plan does not include the ... feature. | The app’s plan lacks that feature | Plan requirements |
This feature is only available for public applications. | Plan Builder and Grow tools need a public app | App types |
... requires two-factor authentication. | The organization enforces 2FA | 2FA |
Demo mode is on. | Writes are off in demo mode | Demo mode |
Refusing because confirm: true was not supplied | The tool needs your decision | Call again with confirm: true once you decide |
Use x_y instead of xY | Arguments are snake_case | Meridian MCP troubleshooting |
Unknown status (webhook_deliveries_list) | A status that doesn’t exist | Delivery statuses |
Too many deploy, rollback, database reset or variable write calls. | 10 such calls a minute | Wait and retry |
CLI
The CLI’s exit codes and JSON error shape are in Errors and exit codes.| Message | Means | Fix |
|---|---|---|
You are not logged in to Meridian., Your Meridian CLI token has expired. | No valid sign-in on this machine | meridian login. See Signing in |
This project is not linked to a Meridian app. | No .meridian/project.json | Linking a project |
Cannot prompt for ... in a non-interactive shell. | A question needs a flag in scripts | From a script or an agent |
sets `provider = "sqlite"`, but the managed developer database is MySQL or PostgreSQL | The template’s SQLite datasource | Prepare Prisma |
so this command would not touch the managed developer database | The datasource doesn’t read DATABASE_URL | Prepare Prisma |
declares no shadowDatabaseUrl | prisma migrate dev needs a shadow database | Prepare Prisma |
was written for a different database engine and cannot apply to MySQL | A SQLite or PostgreSQL migration history | Prepare Prisma |
dev_database_limit_reached | The plan’s developer databases are used up | When the developer database is not there |
dev_database_over_storage_limit | Over the 25 MB limit | When the developer database is not there |
Timed out waiting for the developer database to be provisioned. | The first provisioning took more than five minutes | Run meridian dev again |
Port <port> is already in use. | Another process holds that port | Running your app |
meridian dev is already running for this app | One meridian dev per app | Running your app |
Commit ... is not on any pushed branch. | meridian deploy builds pushed commits only | git push, then deploy again |
cli_upgrade_required | The CLI is too old | Upgrading the CLI |
Webhooks
| Code or message | Means | Fix |
|---|---|---|
| A forward answered 401 or 403 | Your route didn’t verify Meridian’s signature | Retries and permanent failures |
| A forward answered 404, 405 or 410 | No route at the forward path | Retries and permanent failures |
Forwarding disabled for this topic. | The topic has no forward path | Delivery statuses |
No app runtime target resolved for webhook. | No deployed environment to forward to | Where forwards go |
| No delivery at all | Not routed, not registered, or declared in shopify.app.toml | Deliveries |
SDK
The SDK’s error codes (MeridianApiError), what degrades and what throws, are in Errors and degradation.