MetricSign
EN|NLRequest Access
High severitytimeout

Power BI Refresh Error:
JobQueueTimeout

What does this error mean?

A dbt Cloud job run waited in the queue longer than the allowed timeout because all available run slots were occupied by other running jobs, and was cancelled without executing.

Common causes

  • 1Multiple long-running jobs are scheduled at the same time, exhausting the account's concurrent run slots
  • 2A stuck or hung job is holding a run slot and has not timed out yet
  • 3The account is on a plan with limited concurrency and job growth has outpaced the slot limit
  • 4CI jobs triggered by frequent commits are queuing faster than they can complete

How to fix it

  1. 1Step 1: In dbt Cloud, navigate to Deploy > Runs and check for hung or long-running jobs consuming all slots.
  2. 2Step 2: Cancel any stuck jobs manually to free up run slots.
  3. 3Step 3: Stagger job schedules to avoid all jobs starting at the same cron interval (e.g., offset by 5–15 minutes).
  4. 4Step 4: For CI jobs, configure deferral — dbt Cloud can cancel redundant CI runs if a newer commit for the same PR is queued.
  5. 5Step 5: Upgrade the dbt Cloud plan or contact dbt Labs if the concurrency limit is consistently insufficient for the job volume.

Frequently asked questions

What is the dbt Cloud run slot limit?

The limit depends on the dbt Cloud plan. Team plans typically allow a small number of concurrent runs; Enterprise plans have higher limits. Contact dbt Labs to review or increase your account's concurrency limit.

What is CI deferral in dbt Cloud and how does it help?

CI deferral allows a CI job to compare only changed models against the production state, reducing run time. It also lets dbt Cloud cancel a pending CI run if a newer PR commit makes it redundant, preventing queue buildup.

Other timeout errors