Forum Discussion

sgallo's avatar
sgallo
Advocate V
2 years ago
Solved

Data model not finishing refresh

Hi all,   My data models are taking forever to refresh. Some that usually take around 10/20mins are still refreshing after 2hours. Any known issue happening in Power BI/Fabric? Any help is appr...
Need Help
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi sgallo ,

     

    We have seen on the internal platform that other engineers have reported this issue and submitted it.
    The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

     

    Best regards.
    Community Support Team_Scott Chang

ibarrau's avatar
ibarrau
Super User
2 years ago

Hi. You can check status of Fabric servers in here: https://support.fabric.microsoft.com/es-AR/support/

If everything is working ok in there, you might want to check if your capacity is not overloaded. You can do it installing the Fabric Metrics App

I hope that helps,

sgallo's avatar
sgallo
Advocate V
2 years ago

Hey ibarrau ,

 

Thanks for your response. I already checked it and everything looks good. 

I am just confused by the lenght of the refresh as it usually takes max 20 min and now we are at 2h+

 

If you have any more ideas please let me know,

Simone

    • sgallo's avatar
      sgallo
      Advocate V
      2 years ago

      Hey aj1973 ,

      I indeed am:

       

      Thanks for checking this but does not seems to be the issue.
      Simone

      • ibarrau's avatar
        ibarrau
        Super User
        2 years ago

        Hi. As an alternative for checking if the dedicated capacity is overloaded, when using onpremise data, you can have issues with bandwitdh cuts or cpu processing overload (if you have complex operations at power query).

        If all of that is working ok. Try publishing the model to a different workspace and refresh. If it works fast, there might be an internal server problem at the model and the workspace. It can be model cache that will be solved automatically in time or an internal error that also would be fixed in time.

        I hope that make sense.