wow.., this erorr has been happening for the last 1 year.., and nothing has been resolved??
Crazy insane..
I solved it by publishing without doing a test first. Once published I edited the zap and it worked
Any updates on this? Running through the same issue. I just started using zappier, and it barely runs once a week. I can’t possibly be hitting the API limit, not even close.
Confirmed. Thanks @SamB !
No, I am not. My customers get one to two Google Business Profile reviews per week. Hardly an extreme case. In addition there are only five Zaps in our account set up that are triggered by Google. Again, not extreme at all. Thus clearly an issue between Zapier and Google. It is similar to the YouTube issues Zapier is having.
Hey there, @Code4food! I wanted to pop in and see if you were still seeing this error?
If so, I’d definitely recommend reaching out to support as @MohSwellam mentioned. They’ll be able to dig into your logs and hopefully get to the bottom of this with you.
Keep us posted!
Thanks for getting back to me @Dubs24.
The error mentions “Couldn't create a reply for this review” so it appears that the error was only occurring on a Create Reply action and not on the updated New Review trigger itself. So it seems that the new trigger has indeed helped to prevent these errors on the trigger side of things.
As noted previously the team are still working on preventing these quota errors on the actions for the Google My Business. If you replay that errored run of the Zap it should be able to run successfully now. At the moment the bug report still remains open, but once the errors are resolved in the Google My Business actions as well the bug report will be officially closed and we’ll send out and email notification and will post and update here to confirm. 
Thanks for reaching out here @Max Helios.
As mentioned in my previous reply here an updated version of the New Review trigger has been added which should help to prevent these errors in the Google My Business trigger. But a fix has not been found for the Google My Business actions yet. Although, these errored actions appear to be going through successfully when they are replayed later on so I’d recommend replaying any errored actions in the meantime.
I’ve added you to the list of folks that are being affected by these “Quota exceeded...” errors. While I can’t give an estimate as to when it will be fully resolved, you’ll definitely get a notification from us once it is. Thanks for everyone’s continued patience here in the meantime, it’s very much appreciated.
Me Too please, it’s incredible that in two years you didn’t solve this problem.
Thanks for letting us know @Dubs24. I’m very sorry that switching to the new trigger hasn’t resolved the errors as hoped.
Can I just double-check is it that you’re still seeing the error when testing in the Zap editor?
If so, that is to be expected as the new trigger still uses same method as the previous polling version of the trigger to bring in new test records from Google. If you choose the Skip test option and turn on the Zap the trigger should run without running into the same quota errors.
If not, are you getting error email notifications from us stating that the new trigger is also running into these same “Quota exceeded...” errors?
To confirm what has already been said, I changed to the “Instant trigger”, however it’s hasn’t fixed the issue. This still remains a bug.
Hi @gSchettino, I’ve added you to the list so we’ll be in touch by email once it’s been sorted.
For context it’s an intermittent issue that was resolved previously but has resurfaced. The current bug report that everyone is currently added to was opened in September of last year but granted, it’s still a long standing issue!
The team have already released a potential fix for these errors that are affecting the Google My Business trigger and they are working on preventing these quota errors in Google My Business actions as well. It’s recommended that you replay (or enable autoreplay) any errored runs of the Zap as that should allow them to be run successfully in the meantime. 
@SamB that’s correct. I have 6 similar zaps that all use this trigger. About 10 days ago I went in and switched them all to the “new” trigger. Yesterday I received the usual “Couldn't create a reply for this review: Quota exceeded for quota metric 'V4’…...” error on one of my zaps.
@SamB @ken.a it happened again in one of the Zap runs. I received an email about it. However, when I re-tested it myself with the same data it worked fine.
Here’s the link to the Zap history from the email I received: https://zapier.com/app/history/004a78a4-c451-a76b-a45f-550a80cf44f1?utm_source=mailgun&utm_medium=email&utm_campaign=mlgn-gbl-notif-txn-errors_alert&utm_content=action_error
That is most odd @cloudartisan, but I’m glad that recreating the action appears to have resolved the issue for now. 
I’ve added you to the notification list at any rate to help increase it’s priority. We’ll be in touch with everyone impacted by these errors as soon as they’ve been resolved.
@SamB @ken.a if I delete and recreate the action exactly as it was, it starts to work, even if I only got the quota error message recently.
@SamB @ken.a this is happening to me, too. I only just setup the Zap and I’m running the Test Step and getting:
Quota exceeded for quota metric 'V4 General Requests' and limit 'V4 General Requests per minute' of service 'mybusiness.googleapis.com' for consumer 'project_number:466514807953'.
I have tested it 3 times so far, spread across 5-10 minutes. This definitely shouldn’t be a quota issue.
Hi @MarArr,
I have added you to the list of affected members. We will keep you in the loop via email once the bug has been fixed.
I appreciate your patience and understanding.
@SamB Can I please be added to the list of affected people? I have the exact same issue. Thanks!
Hi @Code4food ,
It seems you are exceeding your Quota limits. Google does have a very high API limit though so not sure why you would run into that error. You can read more about the API Limits here
https://developers.google.com/analytics/devguides/reporting/core/v4/limits-quotas
This is in regards to Google Analytics, you can google your app if its not this one to check what are your API Limits
Hello @Habito Dev, @inspectorben, @faaris, @JavierMadreamiga, @Dubs24, @AA GG, @Tunity.be, @Fran LV, @xavierB, @Erica Diaz Team, @HIG, @Kurav13, @Athar A. Khan, @Rohit Kochar and @vnwind.
I’m truly sorry we missed your message here, I’m honestly not sure why we didn’t receive any notifications for them.
This is being worked on but I can’t make any promises as to well it will be resolved by. I can confirm that you’re all definitely on the list of folks being affected by this so you’ll get an email notification from us as soon as it’s resolved. And we’ll be sure to post in the thread here as well to confirm once it’s been fixed.
Thank you all for your continued patience, we’ll post any updates here once we have them.
For anyone who comes across this thread please use the @ mention feature to mention me (@SamB) directly to ensure I get a notification.
same problem here and it is crazy that there is no solution to it.
Hi,
I am facing the same issue. It seems this is a year old problem. As the project number is same for everybody, this seems to be an issue between Zapier and Google Reviews. Please guide if there are any possible solutions.
Error code: Error while retrieving: Unable to retrieve reviews: Quota exceeded for quota metric 'V4 General Requests' and limit 'V4 General Requests per minute' of service 'mybusiness.googleapis.com' for consumer 'project_number:466514807953'.
Thanks,
Rohit
Hello. I received a notification today from Zapier informing me that this issue has been partially resolved by the addition of a new Review Trigger. The email urges developers to switch to the new trigger. However no info has been provided on how to do this and we cannot find the new trigger in the Zap editor.
Could anyone pls shed some light on the correct was to migrate our Zaps to the new Trigger to finally resolve this issue.
Ty in advance
Keith