Forum Discussion
Gen2 Dataflow Issues: Missing Refresh Status and Notification Problems
Our team is currently migrating data pipelines from Gen1 to Gen2 dataflows in MS Fabric. While Gen2 has some advantages, we've encountered several frustrating issues that are impacting our workflow.
Background on Notification Issues: With Gen1 dataflows, error notifications were straightforward; whenever a refresh (scheduled or on-demand) failed, our team received an immediate email notification, allowing us to address issues quickly. From my research, Gen2 dataflows require Power Automate to achieve similar functionality, which adds an extra configuration step.
Main Issue - Missing Refresh Status Information: The primary problem I'm seeking guidance on involves our Power BI online environment. When viewing dataflow summaries in our workspace, the Gen2 dataflows never display:
- "Refreshed" status (even after successful refreshes)
- "Next Refresh" information (even when refreshes are scheduled)
This lack of status visibility makes it difficult to monitor our dataflow health and schedule adherence.
Questions: Has anyone experienced similar issues with Gen2 dataflow status reporting? Are there specific settings or configurations we might be missing that would restore this functionality?
Any insights or workarounds would be greatly appreciated.
Hi SAAR95 ,
You’re not alone this is a known behavior with Gen2 Dataflows, especially for CI/CD-enabled ones.
The workspace view doesn’t reliably show “Refreshed” or “Next refresh” for Gen2 items. This is a limitation rather than a misconfiguration on your side.Workarounds.
- Use Monitoring Hub or Run History.
These provide the most accurate status info for Gen2 refreshes.
Microsoft Docs – Monitoring Dataflows Gen2 - Email Notifications.
Unlike Gen1, Gen2 doesn’t send failure emails by default. You’ll need to set up a Power Automate flow (or similar) to get alerts on refresh failures.
Regards,
Akhil.- Use Monitoring Hub or Run History.
4 Replies
Hi SAAR95
We’re seeing the same behavior after moving to Dataflow Gen2 (incl. CI/CD/Git)The workspace list view doesn’t always populate “Refreshed” or “Next refresh” for Gen2 items (especially CI/CD). For accurate status, use Monitoring hub or the dataflow’s Run history—those are the authoritative views.
Please follow below link in order to find more details regarding above metioned pointer.
https://learn.microsoft.com/en-us/fabric/data-factory/dataflows-gen2-monitor
Email notifications aren’t automatic like Gen1. For Gen2—particularly CI/CD dataflows—you need a notification workflow (e.g., Power Automate) to alert on failures. Community threads confirm the missing built-in email option for CI/CD Gen2.
You can find this solution here
Please follow this and let me know if it helps.
If this helped, please give it a Kudos and mark it as Accepted Solution to help others find it.Thanks
Shashi Paul
Hi SAAR95 ,
You’re not alone this is a known behavior with Gen2 Dataflows, especially for CI/CD-enabled ones.
The workspace view doesn’t reliably show “Refreshed” or “Next refresh” for Gen2 items. This is a limitation rather than a misconfiguration on your side.Workarounds.
- Use Monitoring Hub or Run History.
These provide the most accurate status info for Gen2 refreshes.
Microsoft Docs – Monitoring Dataflows Gen2 - Email Notifications.
Unlike Gen1, Gen2 doesn’t send failure emails by default. You’ll need to set up a Power Automate flow (or similar) to get alerts on refresh failures.
Regards,
Akhil.- Use Monitoring Hub or Run History.
Hi SAAR95 ,
Just checking in were you able to try Monitoring Hub or the Run History to confirm the refresh status? That should give you the most reliable view for Gen2 dataflows. Also curious if you set up any Power Automate alerts yet to cover failure notifications.
Regards,
Akhil.Hi SAAR95 ,
Following up were you able to check the refresh status in Monitoring Hub or Run History? If you’ve also set up Power Automate alerts, that should help catch any failures proactively. Let us know if you’re still facing issues so we can assist further.
Thanks,
Akhil.
