Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I update my datamodels in a sequence where I update my data through stored procedures and after that I refresh the data by pushing the refresh.
But from time to time, not always, it says the refresh has failed due to too many refreshs, but it has only been refreshed 7 times. In the settings I have set the refresh option on the page to local time, but it looks as if the model refresh is counted by a different time than my local time setting. And another thing is that it sometimes seems as if a pushed refresh that fails (for not so obvious reasons) also count as a refresh (but not always) even though the fail is due to external things regarding Microsoft, because a retry shortly after lets the refresh complete with no errors.
So have anyone experienced this before and what was the solution?
Please provide more details. Is that on a Shared or Premium capacity? What do you mean by "push"? Are you initiating the refresh manually in the service or via the API or via XMLA?
We use Pro version. We refresh the reports through API (that is a push in my mind 😊)
Yeah, no. What you do is calling an API and telling it to do its thing. A push is when you supply the actual data that needs to be added to the dataset
Thanks for the correction, but did not help me closer to a solution 🙂
Use the tenant audit log to see how many refresh requests your process actually made.
We did and it only use 7 and we have 8
We never get to that much retries...
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
10 | |
7 | |
3 | |
2 | |
2 |