Monitor duration doesn't match refresh ID

Hello !

Thank you for posting on Microsoft Fabric community.

The Monitor duration is the end-to-end wall-clock time (it includes waiting in the capacity queue, model warm-up...). The Refresh ID time shows only the actual processing once a slot was obtained (Power Query/partition processing + commit, plus query cache).

So if Monitor says 7 to 8 minutes but Refresh ID shows 1 to 2 minutes, the extra minutes are mostly queue or warm-up time because the capacity was busy or just cold.

It is better to use Monitor as the total user wait and Refresh ID as the engine compute time.

• Monitor duration
  includes total job time—like queuing, cache refresh, and post-processing.
  • Refresh ID duration shows only the actual data refresh time (partition processing).
  • That’s why monitor shows ~7 min, but refresh ID shows ~2 min.

  Use monitor for capacity insights, and refresh ID for performance tuning. Let me know if you want a quick visual tracker for both!