Google Calendar connector failing with 403 Rate Limit Exceeded

Question

Sometimes my Google Calendar actions to create/update/delete are failing with error 403 Rate Limit Exceeded. Google's documentation suggests using exponential back-off.

I also have Google Calendar list events actions in the same flow and they also suffer from rate limits but they instead return error 429 and seems like Logic Apps can transparently perform retry with exponential back-off in that case - run details show yellow bar with sttus such as "1 retries occurred".

Looks to me like Google wasn't very consistent with error codes (although at least documented it) and Microsoft missed one case.

Sadly I don't have support contract to report an issue.

What are my options?

Answer 1

The Retry Policy is based on conventional HTTP responses and isn't specific to this action, but a common behavior for all actions. So, a workaround would be to detect the error and loop over the action as required.

This of course would be difficult if required for multiple actions and/or in multiple locations. If it's just for one action, you could extract the section into a separate workflow that you could reuse.

Also, feel free to raise a feature request to address this difference.