Fix a Deployment Stuck in Queued or In Progress on Coolify

Error: Deployment stuck in "Queued" / "In Progress" forever, Force Start doesn't help, no logs appear

A new deployment never leaves the Queued or In Progress state and produces no logs, because Coolify's queue worker has stopped processing jobs, not because your build is slow.

Coolify queues deployment jobs through a Horizon-based worker. If that worker stops processing the "high" queue — commonly after a brief Postgres or Redis blip, or a partial Coolify update — new deployment jobs simply never get dequeued. The UI shows Queued or In Progress indefinitely, with no logs and no surfaced error, because nothing has actually gone wrong with your build; the job just never started running.

The fix

  1. Check that Redis and the Horizon-related containers are up and healthy.

    docker ps --format "table {{.Names}}\t{{.Status}}"

  2. Restart the Coolify stack to reset the Horizon workers.

    docker restart coolify

  3. Cancel the stuck deployment, then manually trigger a new one with Force Start.

  4. Check the server's disk isn't full — queue workers can silently die under disk or memory pressure without surfacing an error.

Verify it worked

A new deployment moves from Queued to In Progress to Finished within the normal build time, with logs streaming live.

Related Coolify errors

Sources

Have Emsden Studio fix it for you — from A$149

All Coolify deploy errors