Forum Discussion

Nagaraj_D's avatar
Nagaraj_D
Advocate I
7 months ago
Solved

Internal service error during Power BI Service refresh – recurring issue

Hi everyone,

 

I’m facing the following error during dataset refresh in Power BI Service:

"The last refresh attempt failed because of an internal service error. This is usually a transient issue."

The issue occurs intermittently (sometimes the refresh succeeds, sometimes it fails).
There are no changes to the dataset, credentials, or gateway configuration.

 

Has anyone experienced this recently?
Are there known causes or best practices to avoid this internal service error?

 

Thanks in advance for your help.

  • This is a known, intermittent Power BI Service issue, and the message is accurate: it’s usually transient. Common causes are:

    • Service-side throttling or capacity pressure (shared capacity is most affected)

    • Backend refresh infrastructure hiccups (nothing wrong with your model)

    • Gateway handshake timing out (even if the gateway is healthy)

    • Heavy refresh operations (large models, many partitions, long M steps)

    Because nothing changed in your dataset/config, this strongly points to service instability, not a modeling error.

     

    The best you could do is to create a pipeline to refresh the semantic models you have and add a retry setting on it.

5 Replies

  • Many dataset refreshing simultaniously can cause an internal error. 

    If you use data gateway, can you check if the connexion is OK ?   

     

    I suggest you open a ticket to microsoft support to help you if still not working. 

    • Nagaraj_D's avatar
      Nagaraj_D
      Advocate I

      Hi AntoineW 
      I have checked the on-premise gateway connection and the gateway status is online

  • This is a known, intermittent Power BI Service issue, and the message is accurate: it’s usually transient. Common causes are:

    • Service-side throttling or capacity pressure (shared capacity is most affected)

    • Backend refresh infrastructure hiccups (nothing wrong with your model)

    • Gateway handshake timing out (even if the gateway is healthy)

    • Heavy refresh operations (large models, many partitions, long M steps)

    Because nothing changed in your dataset/config, this strongly points to service instability, not a modeling error.

     

    The best you could do is to create a pipeline to refresh the semantic models you have and add a retry setting on it.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Nagaraj_D,

     

    Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to AntoineW and cengizhanarslan  for prompt and helpful responses.

    Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

     

    Best regards,
    Prasanna Kumar