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.
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections
on:
Need more details on Average utilization% in Capac...
lbendlin
on:
Increase the 1,000 Item Limit per Fabric Workspace
NaamaTsafrir
on:
Rename "Domain Admin" to "Domain Owner" to match P...