Deploy is greyed out or refused

Another deployment of the service started between the page loading and your press, for example from a push to its branch. Open the service's Deployments tab to follow it. Deploy again once it has finished if you still need to.

The service's organization pays by card and has none on file, so Cloud deploys only the free service and the free database in it. Add a card under Payment method on its Billing, then deploy again. See Payments.

That month's statement reads Payment failed, and Cloud refuses new paid work in the organization until it is paid. Left unpaid past the date in Cloud's email, it also stops the organization's paid services (Stopped for billing). Press Pay now on it under Statements on Billing, then deploy again. An overdue invoice reads "The invoice for November 2026 is past its due date." in the same way: pay it, then deploy.

The organization's paid services are stopped for billing, so none of them is deployed or started until the cause clears. The sentence names the cause and what clears it: a month to pay, a card to add, an invoice past its due date, or the monthly limit, which clears when the next month begins or support raises it. Your free application and free database are never refused for it. Clear the cause on Billing; Cloud then starts again what it stopped, and you can deploy. Payments lists each sentence. A deployment that was building when the stop came reads "Deployment cancelled because paid services in this organization are stopped for billing.": deploy it again once the services are back.

Every cause of the organization's stop for billing has cleared, and Cloud is starting the services it stopped. Deploy again in a minute.

The amounts are the organization's. What its month comes to, with this change, passes its monthly limit; deploying a service that is already running is never refused for it. Stop or shrink something you no longer need, or ask support to raise the organization's limit. The monthly limit explains the figure.

Cahaves suspended the account, which stops the services of all its organizations and refuses changes until the suspension is lifted. Your stored data is kept. Contact support.

A backup of this service is still queued, running or being verified, and a service is not deployed, started or stopped while its data is being copied.

Open Storage, Backups, and find the service in Backup history. Deploy once its run reads Completed or Failed. A run that stays on Needs reconciliation is checked again every minute; if it does not move, contact support.

A volume was attached to the service, and Cloud could not confirm that the platform took the attachment. Until it knows, the service is held.

Open Storage, Volumes (or the service's Storage tab), find the row marked Awaiting confirmation and press Check attachment. Then deploy. See Volumes.

A restore that involves this service has not finished, and the service is held until it does. Restore is not available in the console yet, so contact support with the project and service names.

The workspace of the service's organization is not ready yet. See Your workspace is still being prepared.

Cloud asked the platform and got no answer. Nothing was changed. Press Deploy again in a minute; if it keeps happening, contact support.

The console could not reach Cloud's API at all, so the request was never made. Check your connection, then try again in a minute.

The service was created on a platform Cloud no longer runs it on. You cannot fix this from the console. Contact support with the project and service names.