Forum Discussion
Dataflows not refreshing
The API based issues have the following error output. I have the same code running successfully within a PBI dataset on the same group.
Run Time: Invalid date
Dataflow: ####### - Lookup Tables
Status: Failed
Entity: Boards
Start: 30/11/2018 17:05
End: 30/11/2018 17:05
Failed Error: Internal error Request ID: fc4ee9e1-0593-e23d-1f65-19117de875f6
Activity ID: f6056529-bf86-4f11-ba28-88a01d419e2e
Hi GS-OIT,
Please check the settings of the Dataflow. What I can find is the credential error.
Best Regards,
Dale
- GS-OIT7 years agoHelper I
This seems odd, I have a dataset that requires no connection and is purely generated by M code. This is now coming back with a refresh error. Could the authentication be something to do with Dataflows and Power BI validation rather than with the data source?
Start: 03/12/2018 08:52
End: 03/12/2018 08:52
Error: Internal error Request ID: 1ca7786b-7651-9957-31ff-87f107bfdaa9
Activity ID: f6b2450d-49d3-49bf-9677-9f9a93f46d51
- v-jiascu-msft7 years agoMicrosoft Employee
Hi GS-OIT,
I would suggest you create a new one from scratch. I only found this error. Please check it out or contact the administrator.
>>>Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access 'f3b0741*************41f3f4128'.
BTW, did the error have something like below?
Best Regards,
Dale- GS-OIT7 years agoHelper I
It doesn't give me this information because in the Dataflows it just gives you a download of the errors which don't include the cluster information. It does look like there's something to do with me having multi-factor authentication on my Azure AD and a restriction somewhere in an admin config that is stopping these dataflows refreshing ... but it's not clear from the errors or the message you have shared as to how I can resolve it.
I created another one from scratch with the same issue.
I really apprecaite your help on this, I think dataflows are going to be awesome and they were working for a few days and then just stopped, I will take a look through our admin logs and see if I can see any changes.