We are currently having an issue with workflows that fetch google reviews.

[AnnaLauraHr]

Your Task History ID

https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTZhMDYzZjA0MzY1MjZmNTUzNTUxM2Ii_pc

Hello Pabbly team!We are currently having an issue with workflows that fetch google reviews.

Example: https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTZhMDYzZjA0MzY1MjZmNTUzNTUxM2Ii_pc

We have the "reset on execution = NO" but it continues to pull the exact same reviews. Sometimes it goes back 1 or 2 and then will default to the first one.

We checked the History for this workflow and that is what we see, the same reviews being pulled repeatedly.We are having this issue with many other of the same group of workflows. Please advise

 

[ArshilAhmad]

Hi @AnnaLauraHr,

As mentioned previously, the 'Fetch Reviews' action step does not differentiate between new and old reviews. It could fetch old reviews multiple times. The 'Reset on Execution' feature only sets the priority of the reviews being fetched; it doesn't guarantee that old reviews (or reviews that have already been fetched) will not be fetched again.
https://forum.pabbly.com/threads/ca...tch-or-bug-in-our-workflow.22062/#post-105747

If you want your workflow to be executed only for new reviews, you need to delete the 1st and 2nd steps of your workflow and set up 'GBP: New Reviews' as your trigger step. For your specific use case, using a 'Scheduler' as the trigger step along with the 'Fetch Review' action step is not recommended.

 

[AnnaLauraHr]

Hi @AnnaLauraHr,

As mentioned previously, the 'Fetch Reviews' action step does not differentiate between new and old reviews. It could fetch old reviews multiple times. The 'Reset on Execution' feature only sets the priority of the reviews being fetched; it doesn't guarantee that old reviews (or reviews that have already been fetched) will not be fetched again.
https://forum.pabbly.com/threads/ca...tch-or-bug-in-our-workflow.22062/#post-105747

If you want your workflow to be executed only for new reviews, you need to delete the 1st and 2nd steps of your workflow and set up 'GBP: New Reviews' as your trigger step. For your specific use case, using a 'Scheduler' as the trigger step along with the 'Fetch Review' action step is not recommended.

View attachment 43108

Thank you Pabbly team!
We also have this other version of the workflow that we actually use to fetch new reviews. Is there anything we should be changing on this one to avoid the issue of the same reviews being fetched?
https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTY4MDYzMjA0MzU1MjZiNTUzMTUxM2Ei_pc

 

[Supreme]

Your workflow has been operating without any pending reviews, resulting in the 'ReviewAvailable' task being set to false.

Furthermore, if all reviews have been addressed, you may proceed with using the workflow for any forthcoming reviews on your review page.

 

[AnnaLauraHr]

Your workflow has been operating without any pending reviews, resulting in the 'ReviewAvailable' task being set to false.

Furthermore, if all reviews have been addressed, you may proceed with using the workflow for any forthcoming reviews on your review page.

Thank you for the information, we will try to make some changes based on this.I have another question for you guys.
Can you please let me know what could be causing the partial fail for this workflow? https://connect.pabbly.com/task/his...d=IjU3NjUwNTZhMDYzZjA0M2Q1MjZmNTUzMzUxMzIi_pcIt says "too many attempts", which is a first for us. Any information is greatly appreciated.

 

[Supreme]

Receiving a 'Too Many Attempts' response suggests that the API rate limit has been exceeded. Consider decreasing the frequency of your requests, reviewing the API documentation for rate limit details, and reaching out to the application's support team for assistance with the responses you are receiving.