Forum Discussion
"Too Many Requests" error when scheduled refresh with Google Sheets
I know there's already lots of discussion regarding the "too many requests" API error of the connection of google sheets. But I'm still confused by the error only happens when it's doing the scheduled refresh everyday. However, when I rerun the refresh again mannually when it fails, it won't have this error. Anyone knows why? I'm assuming it shouldn't be the issue of my worksheet cuz it won't exceed the api limits when I run it by myself.
Thanks for any ideas or advice!
- Anonymous2 years ago
Hi, aria233
Based on your question, The problem you may be experiencing is that when you refresh your Google Tables connection on a scheduled refresh, you get the "Too Many Requests" API error, but not when you refresh the connection manually.
When refreshing multiple refresh schedules at the same time, the models used for refreshing are loaded. Once there are too many models in memory, the memory becomes full. Models generated by subsequent refresh operations cannot be loaded and enter a queued state, causing reports to load slowly or fail. You can refer to the following documentation: Schedule refresh sometimes fails for Google Sheets... - Microsoft Fabric Community
To avoid this issue, you can try changing the scheduled refresh time to a time when fewer requests are sent.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
- lbendlin
Super User
Is the structure of your Google Sheets changing frequently? Power Query perceives any small meta data change as a big affront, and will run queries multiple times in quick succession.
- AnonymousNot applicable
Hi, aria233
Based on your question, The problem you may be experiencing is that when you refresh your Google Tables connection on a scheduled refresh, you get the "Too Many Requests" API error, but not when you refresh the connection manually.
When refreshing multiple refresh schedules at the same time, the models used for refreshing are loaded. Once there are too many models in memory, the memory becomes full. Models generated by subsequent refresh operations cannot be loaded and enter a queued state, causing reports to load slowly or fail. You can refer to the following documentation: Schedule refresh sometimes fails for Google Sheets... - Microsoft Fabric Community
To avoid this issue, you can try changing the scheduled refresh time to a time when fewer requests are sent.
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.