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