TWL-KB-034 · Power BI · Maker / builder

Scheduled refresh failed

Check the last successful refresh time before relying on numbers.

Applies to: Power BI service datasets/semantic models.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Refresh failed / credentials or gateway warning. Check the last successful refresh time before relying on numbers.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Refresh failed / credentials or gateway warningThe data model refresh needs investigating at the failed source or gateway. A report that still opens may show old data.Check the last successful refresh time before relying on numbers.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Find the intended model; Read refresh history; Note the failing source; Escalate to the owner
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Find the intended model

    Do this
    Confirm the workspace and semantic model with the owner.
    What you should see
    You know which model is involved.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Read refresh history

    Do this
    Read the failed refresh details and the last successful refresh time.
    What you should see
    An error message and a last good time.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Note the failing source

    Do this
    Record credential, source or gateway details without copying secrets.
    What you should see
    The failing component is identified.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Escalate to the owner

    Do this
    Ask the model or gateway owner to review. Do not replace shared credentials.
    What you should see
    The right owner is engaged.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.