Forum Discussion
No refreshing
- Anonymous2 years ago
Hi ebjim , All,
We are seeing an increase in failures related to upcoming billing and thorttling changes to Fabric artifact's handling of usage > than 24 hours of capacity. At the moment, this applies to US North and UK regions and we're rolling back changes that react to over used capacities ASAP to provide relief in the short term.
I recommend reading the following article, and updating your capacity Metrics apps to better prepare for the eventual enablement of throttling.
We are also accelerating better handling and experiences to help Dataflow customers understand when capacities are over-loaded.
Thank you,
Ben
Seems like this issue solved itself. Had comms with Microsoft and could not find any issues.
For future reference, as suggested by Microsoft:
In these cases, as a next action, we would proceed to collect Browser Traces while recreating the issue for further investigation. Which I think is not possible now.
So, if you see this kind of behavior in future, please try to collect the traces in below way and provide us:
- Here is the process to collect the browser logs:
Navigate to ellipse icon on the browser (3 horizontal/vertical dots)
> More tools > Developer tools > Then find network tab > clear all the pre collected traces (if any) by clicking on clear option
> on the same line Enable preserve log and Disable cache > Then start try refreshing the dataset till it throws an error. > Then export the logs by clicking on export HAR. (download Icon)