Skip to main content
err:unkey:application:deployment_no_current
Example

What Happened?

You called promoteDeployment 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

  1. Deploy to production and wait for the deployment to reach ready.
  2. Once the app has a current deployment, promote or roll back as needed.
  3. Confirm the current deployment with getDeployment: the current one reports isCurrent: 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 ready does not become the current deployment.
Last modified on July 20, 2026