Answered

Scheduled Dataflow refreshes stopped for no reason. 'Next refresh date' is in the past. No errors.

(3) Share

Report

Posted on by Len C

379

I opened a case for this but MS support is not responding after three days. It responded once to ask four questions that were all answered in the Description of the case when I opened it.

In our production environment, our only two data flows scheduled for refreshing Daily stopped refreshing for no reason on March 22nd. There were no errors on the last run on March 21st. I can each dataflow manually ('Refresh Now') with no errors - and have been doing so in order for the data to be processed daily.

But the 'Next refresh' remains stuck on 3/22/2025:

I tried Editing the Refresh Schedule in an attempt to maybe clear out whatever data corruption happened. But cannot Save the updated schedule: saving an edited Refresh Schedule results in an iframe trying to display an error stack, which freezes the entire web page, so I cannot copy the error message nor scroll within the error popup's viewport to read the error details.

It seems the configuration data behind these dataflows has been corrupted. And do not have access to fix it.

Anyone have any ideas? Since Microsoft is not showing up, and there is no way to fix through make.powerapps.com, we may have to rekey these Dataflows completely?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (2)

Verified answer

AmínAA 1,228 Super User 2025 Season 2 on at

Like (1)

Report

Greetings Len C

I see the problem you have… Well, for starters you might want to check if this problem does exist as well in your dev and/or UAT environments. If the problem doesn’t exist, you might want to try and load the solution from Dev again. In case you don't want to push the whole solution, you could just create a hotfix solution, in which you include the same Dataflows that exist in the main solution or create copies, and just load that into UAT and PRO. This should in theory solve your problem without having to push the whole solution, if you don't want to do so.

Optionally, you could just create a scheduled Power Automate that just launches the Dataflow daily… I actually have done this in my latest project since the client wanted to receive what changes were made in a specific table via email, so, that’s just another way you can deal with dataflow executions! And once again, you could do it, just pushing a hotfix solution, instead of pushing the whole solution.

If you like my response, please give it a Thumbs Up. Should this reply solve your question, please mark your post as Solved. Otherwise, feel free to reply to my answer for further help.

Connect with me if you feel like it!

Was this reply helpful? Yes No
Verified answer

Len C 379 on at

Like (2)

Report

I ended up using the available Copy function to copy the original flows into new ones, then setting the Refresh settings. These new copies are working fine, and I can edit their refresh settings without error.

More later...

Was this reply helpful? Yes No
AmínAA 1,228 Super User 2025 Season 2 on at

Like (1)

Report

Glad to hear you've solved the problem @Len C!

It's pretty close to what I've suggested, but I'm guessing you've copied them directly in production instead of doing it in dev first hahaha! Well if you don't have any other problems make sure to mark this post as solved so other people can see how it can be solved. Cheers

Was this reply helpful? Yes No
Len C 379 on at

Like (0)

Report

Following up: I DO have these dataflows in TWO pre-production environments, and they have not broken there.

Years ago when setting these up, they would not import when part of my solutions, so I rekeyed them manually in each environment.

Anyway, something must have gotten corrupted on the Microsoft side with regard to the Refresh Settings, so that Microsoft (nor I) can update refresh settings on the old flows. Still haven't heard from Microsoft but when I do I'll let them know how I worked around it.

Was this reply helpful? Yes No
MB-20051153-0 4 on at

Like (0)

Report

@Len C - Has this issue remained resolved for you? I have the exact same issue you described. However, it continues to pop up. With example like the below. Where the "Next Refresh" is showing in the past and it is impossible to do anything to get it to reset.

The only difference between your environment and mine seems to be - this "glitch" on Microsoft's side impacts my ability to change refresh schedule on every single data flow in my environment. It is getting a bit tedious copying workflows every couple days so that I can get them to refresh again, then reconnecting all the power automate flows.

The error I get when I try to tweak the refresh schedule. Like yourself it entirely locks up the page.

Was this reply helpful? Yes No
Len C 379 on at

Like (0)

Report

@MB-20051153-0 Yikes, no, mine have been ok since I copied the two that were affected. Sorry about this. If your post gives me any ideas about what could be happening, I'll let you know. Let me know what schedule type you chose.

PS: Nice screenshots, thanks for showing the frozen screen

PPS: I did try to see if I could edit the Dataflow-related tables directly but they are read-only at least from the admin UI. Those tables have some columns containing JSON for the refresh schedule. I assume MIcrosoft updates are either corrupting those. A long shot theory: Microsoft updates may have run the same time as my data flows. Maybe try changing what time they run by a few hours, if possible?

Was this reply helpful? Yes No