MetricSign
Start free
High severitygateway

Power BI Refresh Error:
DM_GWPipeline_Gateway_SpooledOperationMissing

What does this error mean?

The gateway queued a refresh job but when the processing engine tried to retrieve it, the operation was no longer in the queue. The spooled job disappeared — typically because the gateway restarted or lost its Service Bus connection between job submission and execution.

Common causes

  • 1The on-premises data gateway service restarted mid-refresh, losing the queued job
  • 2A Service Bus reconnect between job submission and execution caused the operation to be dropped
  • 3The gateway was upgraded or patched while a refresh job was waiting in the queue
  • 4A gateway cluster failover to a secondary node lost the in-flight spooled job
  • 5An antivirus or endpoint security tool terminated the gateway process during job processing

How to fix it

  1. 1Trigger a manual refresh immediately — this error is usually transient and retrying resolves it.
  2. 2Check the Windows Event Log on the gateway machine for service restart or crash events at the failure time.
  3. 3Ensure the gateway machine is not rebooting, patching, or restarting during scheduled refresh windows.
  4. 4If the error recurs, check gateway cluster health — all nodes should be online and running the same gateway version.
  5. 5Update the gateway to the latest version — Microsoft frequently fixes spooling reliability issues in gateway releases.
  6. 6Use MetricSign to detect recurring gateway instability patterns across multiple datasets.

Frequently asked questions

Does this error affect all datasets using the same gateway?

Yes — all datasets routed through the affected gateway will fail simultaneously. Resolving the gateway configuration or credential issue restores all of them at once.

Does this error appear in Power BI Desktop?

No — Power BI Desktop connects directly to data sources. Gateway errors only occur when Power BI Service initiates a scheduled or manual refresh.

Can this error resolve itself without intervention?

No — gateway errors require manual action: re-entering credentials, restarting the gateway service, or correcting the network path between the gateway and the data source.

How long does it typically take to fix?

A simple credential refresh takes 5–10 minutes. Network or firewall issues can take 30–120 minutes depending on your infrastructure access.

Source · learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoot

Other gateway errors