err:unkey:application:deployment_no_currentExample
What Happened?
You calledpromoteDeployment or rollbackDeployment, but the app has no current deployment. Promotion swaps the current deployment over the existing one, and rollback derives its source from it, so both require an app that has already gone live at least once. A brand-new app that has never had a successful production deployment has no current deployment set.
How To Fix
- Deploy to production and wait for the deployment to reach
ready. - Once the app has a current deployment, promote or roll back as needed.
- Confirm the current deployment with
getDeployment: the current one reportsisCurrent: true.
Common Mistakes
- Promoting on a fresh app: Trying to promote or roll back before the app has ever gone live.
- Assuming a failed deploy went live: A deployment that never reached
readydoes not become the current deployment.
Related Errors
- err:unkey:application:deployment_not_ready - When the target deployment cannot serve traffic
- err:unkey:application:deployment_is_current - When the target is already the current deployment
- err:unkey:application:deployment_not_production - When the action requires a production deployment