Forum Discussion
Advocate VRefreshes from SQL over the Gateway taking longer and longer
Advocate VStill not resolved. We're in the process now of adding another gateway server node to our cluster to see if that helps. We've begun getting refresh failures several times a week now where the refreshes don't complete due to the them taking too long. This is new behavior.
I've been working to refactor longer running models, but it feels like a losing battle. For every few seconds I scrape back on an individual model, the overall trend continues to go up. I finally found a good visual to show it and there's a drastic jump in November 2024--and that's when we fully moved off the June 2024 version of the gateway. Something changed with the gateways then and has only gotten worse since that change.
Community SupportHi motoray ,
Did you get a chance to raise a support ticket? The support team can investigate the issue further on the backend. If you’ve already submitted one, please wait for their response.
Thank you.
- v-menakakota
Hi motoray ,
As you've raised a support ticket, please allow the support team some time to investigate the root cause and provide a solution.
Best Regards,
Community Support Team - motoray
I did finally put in a ticket today. After digging through logs and watching the behavior for a while, I felt like I had enough data.
The last bit of information I found last week is that it seems to be scheduled refreshes on the hour or half hour that have the biggest issues. I have some instances where I have one report scheduled to do a full refresh at a given time and it takes 10 minutes or longer on the schedule, but less than a minute if I do an on-demand refresh at a different time. This doesn't point to a problem with our reports, but with the service itself.
Also worth noting is that my tenant has not shifted to a Fabric capacity yet as our EA kept us on Power BI Premium.