High severitygateway
Power BI Refresh Error:
DM_GWPipeline_Gateway_SpooledJobTimeout
What does this error mean?
The refresh job waited too long in the gateway's queue before execution began. The gateway was overloaded, and the job expired before it could start processing.
Common causes
- 1Too many datasets are scheduled to refresh simultaneously, overwhelming the gateway
- 2A long-running refresh from another dataset is occupying all gateway threads
- 3The gateway machine has insufficient CPU or memory resources
- 4The gateway service was briefly unavailable and jobs queued up
- 5A single large dataset is monopolizing the gateway for an extended time
How to fix it
- 1Stagger your refresh schedules so multiple datasets do not start at the exact same time
- 2Check the gateway machine's CPU, memory, and disk I/O — consider upgrading hardware or moving to a larger VM
- 3Add a second gateway node to the gateway cluster to distribute the load
- 4Identify which datasets take longest to refresh and optimize their Power Query to reduce query volume
- 5Review Power BI Premium capacity metrics if you're on a Premium workspace — capacity saturation causes gateway queuing
- 6Use MetricSign to track refresh duration trends and catch when a dataset starts taking longer than its baseline