Skip to main content
Clever Cloud Status
Back to incidents

Deployments experiencing issues

Incident #1104

Fixed · Deployments · Global

Resolved:

We are currently experiencing issues with deployment statuses. Applications that are already running are unaffected. Our team is investigating the problem. We will provide an update within the next 30 minutes.

Updates

Investigating
oldest

We are also aware of an issue where deployments using build cache (on Pico / Nano instances, or dedicated build instances) are failing and instead building on the runtime instance. This may cause delays in application deployments and / or deployment failures.

Our team is actively working to identify the root cause and resolve the issue. We will provide an update within the next 30 minutes.

Identified

We have identified the issue affecting deployments statuses in the web console and deployments using build cache on Pico / Nano instances or dedicated build instances.

Customers experiencing deployment failures or delays due to missing build cache feature are advised to disable dedicated build instance (application's informations -> uncheck "disable dedicated build instance") and use an instance size that support building the project.

Our team is working to resolve the issue as quickly as possible.

Identified

The issue affecting deployment statuses in the web console has been resolved. However, deployments using build cache (on Pico / Nano instances, or dedicated build instances) are still failing and building on the runtime instance instead, which may cause delays or failures.

Customers experiencing these issues can disable the dedicated build instance (application's information -> uncheck "disable dedicated build instance") and use an instance size that supports building the project.

Our team continues to work on resolving the build cache issue as quickly as possible.

Fixed
most recent

The issue with build cache has been resolved. Deployments should now proceed correctly. Customers who modified their configurations to work around this issue can revert to their original settings.

Affected Components

Deployments
Operational