Forum Discussion

wc123's avatar
wc123
Icon for Helper I rankHelper I
6 months ago
Solved

Refresh Issue

I am having an issue with my semantic model refreshes. I have multiple semantic models that refresh every moring. This moring a few took a bit longer than usual, I mannually cancelled them then threi...
  • SamInogic's avatar
    6 months ago

    Hi,

     

    As per our understanding, you had multiple semantic models refreshing in the morning. A few were taking longer than usual, so you manually cancelled them. Now, when you click Refresh now, you see the “Preparing to refresh” message in the top right, but the refresh never actually starts for some models — while others refresh normally.

    This behaviour is usually caused by a refresh process that is still running in the background, even though it appears cancelled in the UI.

    Why This Happens

    This commonly occurs due to:
    • The cancellation not fully completing on the backend
    • Capacity resource contention (Premium/Fabric capacity overload)
    • A refresh job stuck in a “Cancelling” state
    • Temporary Power BI Service backend delay

    What You Can Do

    Check Refresh History
    Open the semantic model → Refresh history.
    Look for:
    • Status still showing “Cancelling”
    • Long-running refresh
    • Overlapping refresh attempts

    If it’s still in progress, you must wait until it fully completes or fails.

    Wait 10–20 Minutes
    Even after clicking Cancel, the service may still be:
    • Releasing memory
    • Rolling back transactions
    • Clearing locks

    Trying to start immediately can cause the “Preparing” message with no actual execution.

    Check Capacity Metrics (If Premium/Fabric)
    If you're using Premium or Fabric capacity:
    • Go to Capacity Metrics App
    • Check CPU and Memory pressure
    • Look for queued refreshes

    Most Common Cause

    In 90% of cases, this happens because the refresh is still terminating in the background, even though the UI shows it as cancelled.

    Recommendation

    Wait until the refresh history clearly shows Completed/Failed (not Cancelling), then retry.
    If it remains stuck for an extended period (1+ hour), open a Microsoft support ticket with the Activity ID from refresh history.

     

    Hope this helps.

     

    Thanks!