Bitbucket Pipeline Stuck or Queued

How to fix it

Try these in order — the most common fix is first.

1. 1. Check the status page

   1. Open bitbucket.status.atlassian.com and look for Pipelines incidents
   Did this fix it? Yes No

2. 2. Check minutes and runners

   Copy steps
   1. Verify remaining build minutes
   2. For self-hosted runners, confirm the runner is online and labels match the step
   Did this fix it? Yes No

3. 3. Stop hung steps

   Copy steps
   1. Set max-time on steps so they fail fast
   2. Review logs of the stuck step, especially docker build and dependency downloads
   3. Stop the pipeline and re-run
   Did this fix it? Yes No

4. 4. Contact support

   1. If queued with minutes available and no incident, open an Atlassian Support ticket with the pipeline URL
   Did this fix it? Yes No

Symptoms

Steps stay Queued for 15-30+ minutes, or run for hours with no logs, sometimes ending 'Step exceeded processing limits and has timed out'.

Why it happens

• Atlassian incident delaying pipeline starts
• Workspace out of build minutes
• Self-hosted runner offline or labels not matching
• Docker build or download hanging; default step limit is 120 minutes

This guide also covers

• bitbucket pipeline stuck
• bitbucket pipelines queued
• bitbucket pipeline not starting

Other Bitbucket errors

• Bitbucket Permission Denied (publickey)
• Bitbucket App Passwords Deprecated: Switch to API Tokens
• Bitbucket Authentication Failed on Git Push
• Bitbucket Pipelines Build Minutes Exceeded
• Bitbucket Pipeline Exceeded Build Time Limit
• Bitbucket Repository Over the Size Limit
• How to Cancel Bitbucket Subscription