Forum Discussion

Shanshan_Jin's avatar
Shanshan_Jin
Frequent Visitor
7 years ago

dataflow refresh failed due to internal error

Some of my dataflow failed to refresh du to the following error.

Error: Internal error Request ID: 0cc50b5e-342d-1e1d-9943-20caafa209ec Activity ID: 85c08efc-8181-4c2d-a081-c1c512dd3e32

 

This is the first time I met with this stiuation. They used to work well during the past 2 weeks. But failed this morning.

Please help to see what I should do to fix them. Thx a lot

7 Replies

  • Experienced the issue all of a sudden after weeks of successfully completed scheduled refreshesand on-demand refreshes.
    In my case, the cause was hidden in the settings / credentials.
    Was difficult to spot because the "Data source credentials" section inside settings takes some time to enable.

     

  • Hi there

    Can you check if your account had got Multi Factor Authentication enabled?

    If so that is the cause of the error.
  • Hi Shanshan_Jin  & GilbertQ 

     

    I have a similar error and disabled the multi-factor authentication but no luck!

     

    Again, I can refresh within the Power Query online editor but no scheduled or on-demand refresh works.

     

    Has anyone tested if Web.Contents function can refresh Dataflows on demand or via schedule?


    My error log shows below, do these error ID's give ideas about why this fails?

     

    Run timeDataflow nameDataflow refresh statusEntity nameStart timeEnd timeEntity refresh statusError
    Invalid datePUPL2019FailedPU Profit & Loss13/04/2019 22:3113/04/2019 22:32FailedError: Internal error Request ID: ffd1ad8c-407f-5cea-34ab-0fe9fa15c4c3 Activity ID: 8f31c8e0-4271-47f4-860f-ca74b97e1131
    • GilbertQ's avatar
      GilbertQ
      Super User
      Hi there

      Have you tried to create the dataflow again from the start?

      If that fails I had to log a support ticket request for the Power BI team to investigate.
      • Shanshan_Jin's avatar
        Shanshan_Jin
        Frequent Visitor

        Hi GilbertQ,

        The problem fixed automatically after failed for 3 or 4 days (include a weekend). I did nothing during that time. And it didn't happen again recent days.

        Thanks a lot for taking care of it.