Send Refresh Failure Notifications to Distribution List

When a calculation error exists somewhere in the model, a refresh can't be performed. Suggestions: (a) Check calculations first before refreshing tables to speed up the failure getting returned. (b) Improve error messages so they are much more clear - currently they are very generic. (c) Show a warning indicator at table level if any column has an error, which will save time from expanding every single table to hunt for issues.

Auto-refresh failures only 'alerts' the owner & not the team working on the reports.

we had a frustrating issue today. For some reason, 2 of our tables had a relation defined between them (not sure how it happened. All tables are generated based on Kusto queries, and there is no logical relation between them), and today all our refresh attempts failed (Locally and in the dashboard). There was no indication that the reason for failure was due to that relation. After refreshing all graphs one by one (I have about 30), I saw the reason for the failure: Today, the column which was chosen as the FK received 2 similar values. Why didn’t I get this notification when I refreshed the entire report? The failure reason I got was very vague (General DB failure message which I saw only when I refreshed locally. Far away from the detailed message I got when I refreshed the specific graph). I removed the relation and that resolved the issue . If possible - I suggest you’ll add the detailed failure reason to the Refresh failure reasons

I only get an email notifying that a refresh failed for the entries in the 'refresh history' where there is 'failure message' for a failed refresh. please send refresh failure email whenever the status is 'failed'

Many errors contain the value {FieldValue}. This implies that there is a space where an error message could have been added, but was not. Error messages should be a required part of the feature.

Include a link in the body of the Refresh Failed email notification to the actual dataset that failed in order to save time trying to figure out which workspace a dataset resides.

On the refresh failed email, you really need to both include a link to the failed dataset (would save much time) and include what the workspace name is that the dataset came from. I'm in 50 workspaces and it's a guessing game sometimes... :/

Please vote for this other version of the same request: https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/19965952-enhance-refresh-failed-email-notification-to-inclu

YES!!! We have Dev, Test, UAT, and Production environments. A message that "refresh failed" without indicating which workspace is extremely aggravating. Almost as bad as "Publish succeeded" without indicating which workspace it was just successfully published to. WHEREVER YOU MENTION THE NAME OF A PROJECT, YOU MUST ALWAYS MENTION THE GROUP WORKSPACE TOO.

Hey! As an interim solution, I blogged about this. A nice PowerShell work around to retry and 'alerts' on failed dataset refreshes. https://www.sqlshack.com/manage-power-bi-dataset-refresh-failures/