Statuses

App statuses

The status next to an app's name, in the app list and on the Overview:

Status	Meaning
N/A	The app has just been created and the platform has not reported on it yet.
Creating	The app has no running instances yet: its first image is being built, or its first instances are starting.
Updating	A change is being rolled out — a new build, new instances — or a stopped app is starting.
Running	Every instance the app should have is ready: its port accepts connections.
Degraded	Some instances are not ready; or a new version did not roll out — its build failed while every instance of the previous version was ready, or its instances never became ready — while the previous version keeps serving.
Stopped	The app runs no instances: it was stopped, or KEDA scaled it to zero.
Error	The build failed while the previous version was not ready on every instance — or while the app was stopped; or no instance is ready and the platform does not expect that to change by waiting: the instances keep crashing, cannot be placed on the cluster, cannot get their disk or cannot pull their image.

Right after you start, stop, restart or deploy an app, the status shows Starting, Stopping, Restarting or Deploying until the platform reports on the app again.

The app's status follows the app itself; a slot in trouble does not change it.

Slot statuses

A slot's status, shown on the Slots tab and on the slot's page, uses the same names as an app's, with some differences:

• A new slot shows Pending until the platform reports on it.
• A slot whose build fails shows Error, even while its previous version keeps serving.
• A slot whose new version never becomes ready is not shown as Degraded for that.
• A slot whose instances cannot get their disk or cannot pull their image does not show Error for that.

Where to find the reason

• The Operations tab lists the platform's work on the app. An operation that failed carries the reason — for example that the instances crash-loop, with their last exit, or that they cannot be scheduled — see Operations.
• The Deployments tab shows each deployment's message, and its build log — see Deployments and revisions.
• The logs show what the app itself wrote before it stopped.
• An app whose instances do not start because of a secret is covered in Troubleshooting secrets.

When a new version never becomes ready, check that it listens on the app's Port: the operation then says that the new instances never passed the readiness check on that port — see Port.

Deployment phases

The Phase of an entry on the Deployments tab:

Phase	Meaning
Building	The image is being built.
Succeeded	The build finished; also the phase of a redeployed earlier image.
Failed	The build failed.
Pending	A new container image was set.
Superseded	A newer deployment began while this one was still Building or Pending.

The phase records the build, not the rollout: an entry stays Succeeded or Pending whether or not the new instances became ready. How the rollout went is in the app's status and on the Operations tab.

Certificate states

The certificate of an app with Let's Encrypt on has its own state — see Certificate status.