# Refused deploys

URL: https://getflowing.ai/docs/troubleshooting/blocked-deploys

Why GetFlowing refused to start a deploy: a plan limit, the free app's limits, an unpaid plan or security findings, and what to do about each.

These messages mean the deploy did not go out. For plan, billing and free-app limits, nothing was built. When security findings block a release, the image was built, but nothing went live.

## A plan limit was reached

> You've used your 300 monthly deployments.

> You've used your 500 monthly build minutes.

> Your Starter plan allows 1 app.

> Your Starter plan allows 1 running app. Remove one or upgrade before deploying another.

For deployments and build minutes, the month's allowance is used up: wait for it to reset, or move to a bigger plan. For apps, your plan's number of apps is reached: take an app offline or delete one, add an extra app from **Usage & billing**, or move to a bigger plan. A rollback counts as a deployment, so once the month's deployments are used up, a rollback is refused too. See [Plans, credits and limits](https://getflowing.ai/docs/account/plans).

> Your workspace is over the limits of your Starter plan, so new builds and agent work are paused. Take an app offline, add capacity, or move to a bigger plan from Billing.

Nothing has been taken offline or deleted. The message says what to change. Where the workspace has more apps than its plan allows, it says how many to take offline or delete, and ends with how many extra apps would let you keep them instead:

> Or add 1 extra app from Billing.

Bring the workspace back within its plan's limits, and new builds start again. A rollback still works while the workspace is over its plan's limits, as long as the month's deployments are not used up.

> You've used your AI credits for this month. Add capacity from Billing, or upgrade, to keep the agent working.

> You've reached your 20 monthly agent tasks.

The agent's allowance for the month is used up. Add capacity from **Usage & billing**, or move to a bigger plan.

A deploy is also refused if it would take your apps' estimated hosting cost over your plan's monthly budget. Take an app offline, or move to a bigger plan.

## The plan is not paid

> Your subscription is past_due; expensive actions are paused until it's active.

Update your payment details under **Usage & billing**, in **Manage billing**. See [Billing](https://getflowing.ai/docs/account/billing).

## The free app

> Your free app has had its 10 deploys and imports for today. Try again tomorrow, or keep it live from Billing.

> Your free app’s days are over. Keep it live from Billing to deploy it again.

Choose **Keep it live** on the app, or the Deploy plan in **Usage & billing**, to keep deploying. See [The free deploy](https://getflowing.ai/docs/deploy/free-deploy).

## Security findings block the deploy

Where an owner or admin has made security findings block deploys, a release with findings at or over the workspace's **Severity threshold** does not go out:

> 2 security findings meet the workspace blocking threshold. Review them on the app's Health tab.

> Security review is pending for this exact release. Open the app's Health tab to follow the scan, then retry deployment.

For findings, fix them on the app's **Health** tab and deploy again. A finding that is a false positive stops counting only when a person dismisses it there.

If the review is pending, the scan of this release has not finished: a deploy waits a while for it before it is refused. Follow the scan on the **Health** tab, and deploy again once it has finished.

A release is also refused when a check the scan needs could not run. The message names the check. Look at the scan on the **Health** tab, and scan again.