Running and Deployment Statuses

From any environment window on your Qovery Console, you can monitor the running and deployment status of your environments and services.

Application

ItemDescription
1The dot next to the name of the environment shows its overall status.
For more information, see [Environment Statuses][#environment-statuses].
2The dot in the Service column shows the status of the related service.
For more information, see [Service Statuses][#service-statuses].
3The label next to the name of the environment shows the overall status of your deployments in that specific environment.
For more information, see [Deployment Statuses][#deployment-statuses].
4The label in the Service column shows the deployment status of the related service.
For more information, see [Deployment Statuses][#deployment-statuses].

Run Statuses

Thanks to run statuses, you can find out which services are currently running on your platform, and which ones are interrupted. There are two types of run services available at the moment: environment statuses and service statuses.

Environment Statuses

When you access an environment on your Qovery Console, you can check its status in real time. To do so, at the top of the environment window, hover over the status dot next to the environment name.

The environment status is computed based on the statuses of all the services in that specific environment. Here are all the possible environment statuses:

StatusDescription
STOPPED (Gray dot)All the services are stopped.
STARTING (Loading Icon)At least 1 service is starting.
STOPPING (Loading Icon)At least 1 service is stopping.
RUNNING (Green dot)All services are running correctly.
ERROR (Red dot)All services are in error status.
WARNING (Orange dot)At least 1 service is in error status (but not all of them).

Service Statuses

When you access an environment on your Qovery Console, you can check the status of each service in that environment in real time. To do so, hover over the status dot next to the service name.

Here are all the possible service statuses:

StatusDescription
STOPPED (Gray dot)All the application instances are stopped.
STARTING (Loading Icon)At least 1 application instance is starting.
STOPPING (Loading Icon)At least 1 application instance is stopping.
RUNNING (Green dot)All application instances are running correctly.
ERROR (Red dot)All application instances are in error status.
WARNING (Orange dot)(Valid for multi-instance applications only) At least 1 application instance is in error status (but not all of them).

Deployment Statuses

When you access an environment on your Qovery Console, you can check:

  • the overall status of your deployments in that specific environment, thanks to the label displayed next to the environment name. This corresponds to the status of the last deployment performed on the environment.

  • the deployment status of each service in that specific environment, thanks to the label displayed in the Service column. This corresponds to the status of the last deployment performed on the service.

Here are all the possible deployment statuses for both environments and services:

  • QUEUED (temporary state).
  • BUILDING (temporary state).
  • DEPLOYING (temporary state).
  • DEPLOYMENT ERROR (temporary state).
  • CANCELLING BUILDING (temporary state).
  • CANCELLED (temporary state).
  • DEPLOYMENT OK (final state).

OK, but what really happens when I redeploy an application?

When deploying a new version of an application, Qovery applies a rolling restart methodology. This means that Qovery waits until the new version of the application is up-and-running before killing the previous one.

Likewise, when deploying a new version of a multi-instance application, Qovery follows the following workflow:

1) Deploy new version of instance #1.

2) New version of instance #1 is running => kill previous version of instance #1.

3) Deploy new version of instance #2.

4) New version of instance #2 is running => kill previous version of instance #2.

And so on...