unkey/data/deployment_not_found

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "The requested deployment does not exist.",
    "status": 404,
    "title": "Not Found",
    "type": "/errors/unkey/data/deployment_not_found"
  }
}

​

Likely causes

• The deployment ID has a typo. Deployment IDs start with d_.
• Your root key can’t read the deployment. The get, promote, rollback, stop, and start endpoints return this 404 instead of a 403, so it’s as likely a permission problem as a wrong ID. A key that can read the deployment but lacks the action gets a 403 err:unkey:authorization:insufficient_permissions that names the missing permission.
• For a redeploy with deployments.createDeployment, the source deployment is from a different app or environment.
• The deployment is in another workspace.

​

How to fix

1. List deployments with deployments.listDeployments and use the returned ID.
2. Check that the root key has the right permission: read on the deployment for deployments.getDeployment, read on the deployment’s buildLogs for deployments.listBuildLogs, write on the deployment’s environment for deployments.promoteDeployment and deployments.rollbackDeployment, or write on the deployment for deployments.stopDeployment and deployments.startDeployment.
3. For a redeploy, pick a deployment from the same app and environment you’re deploying to.

​

Related errors

• err:unkey:application:deployment_not_ready: the deployment exists but isn’t ready.
• err:unkey:data:environment_not_found: the environment doesn’t exist.
• err:unkey:data:app_not_found: the app doesn’t exist.