Forum Discussion

Nazirahmed1982's avatar
Nazirahmed1982
Frequent Visitor
3 months ago

power BI dataflow refresh failed due to unknown error

Power BI dataflow refresh fails randomly due to this error every altenate refresh and also it doesn't fail at the same sep/query. it fails at random queries every time with this unexplained error.

 

what could be the reason and how to overcome this.

 

Error: We encountered an error while performing the refresh. Please try again. If the issue persists contact Support. Request ID: 39d8f523-f0e9-4109-9d53-f36376d10ede Activity ID: e12b39b3-3567-47ee-b6d6-44deeeab66b3

12 Replies

  • Hi Nazirahmed1982,

    The message you provided is from the refresh history? This error seems not related to the power query steps.
    Can you please check below things?

    1.Dataflow using any on-prem/cloud gateway connection? If yes weather the gateway status up and running when dataflow is refreshing.

    2.On the same time frame any other dataflow running which using the same source?

    for more clarifination can you provide the power query steps, So we can check more cearly.

    Thanks, 

  • Yes Dataflow is using on-perm gateway and gateway up is online and up and running at the time and always on. No there is no other dataflow running at the same time which is using the same source.

     

    I have only 2 steps in the power query. first step is a simple select query on the view and second step is data type coversion on a couple of ID columns to integer.

     

    After refresh failure if we rerun it, then it scuceeds sometime. It fails random and succesds randomly.

     

     

    • Lodha_Jaydeep's avatar
      Lodha_Jaydeep
      Solution Sage

      Does this is the gen2 dataflow? If you are using gen1 please conver it to Gen2. Also, can you please update the source settings again from the settings and re-register your on-prem connection. And check to see if it resolve the issue or not.

      • Nazirahmed1982's avatar
        Nazirahmed1982
        Frequent Visitor

        Thanks Lodha_Jaydeep Yes the dataflow I am using is using Gen1 dataflow. I will not be able to use Gen2 as the organiosation doesn't approve us to use premium capactiry workspace. is there any other option ? what is the reason that Gen1 errors ? Does this mean that Gen1 will never work properly anymore.

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi Nazirahmed1982,

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.


    Lodha_Jaydeep ,Thanks for your prompt response

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi @Nazirahmed1982,

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

  • v-prasare's avatar
    v-prasare
    Community Support

    We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
    If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.
    Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

    Thank you for your understanding and participation.

  • This usually isn’t a single broken query but a transient or resource-related issue.

    Most common causes are gateway/resource pressure, API/DB throttling, or timeouts under parallel refresh. That’s why a different query fails each time.

    Try reducing parallelism, splitting the dataflow, and checking query folding. Also review refresh diagnostics to catch the exact step when it fails.