Forum Discussion
Google Analytics issue: Request failed (403): Quota exceeded
Same problem here.
Rasing the query limit in Google developers console for my own projects has no effect. Projectnumber in the error does not match any of my own, and I'm no where near the limit for my own projects.
Hi all,
I just wanted to follow up on this issue. I raised a support ticked with Microsoft, and after a thorough search of posible errors, the conclusion was as follows:
All API calls form Power BI Service to Google Analytics are processed under a shared project id handled by Microsoft. The product team is aware of the limitations this is causing to the clients, but they currently can't provide a garantied work around. Their current recommendation is: "try rescheduling the refresh to another time of day if possible".
I hope Microsoft will be able to sort it out with Google soon. I'm still hitting this error frequently each week. For now I'll will go with some extra backup refreshes on differnt times during the day, and hope at least one of them succeds.
Please find the repsonse from the Power BI Product Group Team below:
I have discussed with our PG Team regarding error that you have received " GoogleAnalytics: Request failed (403): Quota exceeded for quota group 'default' and limit 'Queries per 100 seconds' of service 'analytics.googleapis.com' for consumer 'project_number:664933364861' and below are the comments sent on that error by our PG Team.
"Microsoft use two different client ids, one for PowerBI.com (664933364861) and one for PBI Desktop. All customers under PowerBI.com run under the same id. The client Id in the error mentioned is for PowerBI.com, and as you can see the quotas are already set quite high. In fact there's no way for us to increase them further. We've been in contact with Google in the past about getting a special exemption to the quotas, but there was some blocker, I believe it was due to technical issues. As of right now we can provide no guaranteed work around. I'd recommend try rescheduling the refresh to another time of day if possible".
Best,
Torben
Thanks TorbenL for sending the ticket i was thinking about sending one.
This makes sense as it's more sporadic when the refreshes fail as they don't fail all of the time. It seems like having this under a shared project id is a bad solution for Google to be able to cope with. I wonder if it's better to split the user base across multiple shared project ids but i don't know from Microsofts side if that's not viable.
I agree hopefully they can sort this soon as even one smaller amounts of reports it can be a problem.
Whoa, thanks for the reply! I'm happy to get some more clarification on this matter, finally. It does show how sticky this situation is... If it's a structural limit and not a spontaneous bug, this will have huge impact on the services we provide.... Creating Google Analytics reports for customers is actually part of our business. But if we've hit the ceiling here, with no clear roadmap on lifting it, that business is practically over...... Simply refreshing reports on a different time of the day, of different day of the work, will not suffice and it will not save that business. I'll have to make some calls now....
I hope the Power BI team will be straightforward with their customers/users and provide this knowledge as generally available. I mean, it's kind of a big deal.
