The Refresh Attempts feature automatically pushes 3 consecutive refreshes on a dataset if it fails a single time, in hopes that it will succeed. This is helpful, but incredibly wasteful when considering the cost of each refresh due to cloud infrastructure costs.
This feature has quadrupled our cost of refresh failures, because typically when a refresh fails, it is for a valid reason, so the subsequent refreshes fail. This is especially problematic when cloud issues cause refreshes to fail for our entire tenant, effectively causing us to reach our cloud infrastructure cost quotas.
I propose that the refresh attempts feature should be able to be toggled on or off by Tenant, Workspace, or Dataset.
1 Comment
- mganeshphaniFrequent Visitorit would be much nicer if we can specify the type of error, so powerbi can do a exception.contains("error text supplied by customer") to choose to retry or not
Recent ideas
Allow Managed Private Endpoint to be disabled/enabled per notebook
Could notebooks have an option to use or not use the workspace's Managed Private Endpoint (MPE)? MPE can significantly increase notebook startup time, even for notebooks that don't need private conn...frithjof_v20 hours agoCommunity ChampionNew23Views1like0CommentsMatrix: column totals as a bar chart docked to the edge
What's missing Data bars already work on the Total row and column through conditional formatting, so row totals can be read as length. Column totals cannot: they render as a horizontal bar inside a ...Sayurivalente1 day agoRegular VisitorNew80Views6likes1Comment