Lookup Spreadsheet Rows Resourced Exhausted

[ichilddev]

Dear Community.

We got this issue (attached) and wondering how the lookup could result in exhausted resource? We google the error 429 and it shows that there could be more than 300 requests per limit https://developers.google.com/sheets/api/limits. Kindly advise how we can avoid this situation?

 

[PabblyMember4]

Hey @ichilddev

Please share the workflow link so that we can review the workflow setup you have done and will suggest you if it can be more optimized.

 

[ichilddev]

hi this is the Task ID.

IjU3NjcwNTZkMDYzMTA0MzA1MjY0NTUzMzUxMzE1MTYxNTQzNyI_3D_pc​

 

[PabblyMember4]

Thanks for sharing the task id. We will check with the team if we can optimize the workflow. We will keep you updated on the status of this conversation.

 

[ichilddev]

We have another Task that fails to search for a value in Google Sheet, despite the value in the right column.

IjU3NjcwNTZjMDYzNjA0M2M1MjZlNTUzNDUxM2I1MTY3NTQzOCI_3D_pc

Thanks for sharing the task id. We will check with the team if we can optimize the workflow. We will keep you updated on the status of this conversation.

Hi

Any updates?

 

[ichilddev]

Hi Any issue

IjU3NjcwNTZmMDYzNzA0MzY1MjY5NTUzMDUxMzM1MTY1NTQzNSI_3D_pc

We kept having this issue.

 

[PabblyMember4]

Hey @ichilddev

We have already informed the technical team about this issue. If in the future our team will going to optimize this feature then we will let you know.

 

[ichilddev]

Hi hi

This issue surface again. RESOURCE_EXHAUSTED

IjU3NjcwNTZlMDYzNjA0M2Q1MjY0NTUzMzUxMzM1MTYxNTQzOCI_3D_pc

 

[ichilddev]

Same Issue but another Task ID on same day

Task ID IjU3NjcwNTZlMDYzNjA0M2Q1MjY1NTUzNjUxMzI1MTZiNTQzNyI_3D_pc

 

[PabblyMember4]

Hey @ichilddev

This is not related to our project quota for the Pabbly Connect project.

A few months back the same issue appeared with multiple users.

When we contacted Google Team about it. They mentioned that in cases like these we have to use an exponential backoff algorithm to retry the same action in a few seconds.

We have implemented the exponential backoff mechanism after their suggestion. It is currently already live on the Lookup action.
Today's issue is definitely appearing for multiple users but we do not have a way to resolve this from our end.

When we see our overall usage quota for our project, we are well within the limits of the project. I am attaching the screenshot of our usage quota and you can review the percentage being used at the global level for our app.

If someone has faced the same issue and resolved it in some way, do let me know and we can implement the same. Last time, the same issue also appeared for Gmail action, and that auto-resolved itself in a few hours.