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
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v5 hours agoCommunity ChampionNew612Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v13 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019716 hours agoFrequent VisitorNew6Views0likes0Comments