Rate limit for writes exceeded when patching using GAAudiencesUpdater
tyroneschiff opened this issue · 5 comments
I am using the GAAudiencesUpdater to update audiences. The GAAudiencesUpdater seems to handle the creation of the audiences the first time fine, however, when the pipeline runs on subsequent days and uses the patch method the job fails every time.
The error I'm getting is: Unexpected error: HttpError: <HttpError 403 when requesting https://www.googleapis.com/analytics/v3/management/accounts/xxx/webproperties/UA-xxx-17/remarketingAudiences/xxx?alt=json returned "Quota Error: Rate limit for writes exceeded.">
Screenshot from the CRMint attached.
Would appreciate any guidance on why this may be the case with the patch method specifically? Thanks!
Also submitted to Stack Overflow
Honestly, I would avoid using CRMint, there is a lot of bugs and seems no one is maintaining this repo now.
Hi @PA-Mousset, thank you for your honest — though somewhat discouraging — feedback.
At the moment, CRMint core team is busy with migrating CRMint to Google App Engine Standard environment for Python 3.
CRMint is an open-source project, and anyone can contribute to it by submitting:
- feature requests,
- detailed bug reports,
- pull requests aimed at:
- fixing the bugs,
- implementing new features, and
- improving the documentation.
Please, get familiar with CRMint Contributor's Guide to learn more and start contributing to the project.
Fixed by #204.
Thank you @tyroneschiff and @PA-Mousset for reporting this issue: it helped to find and fix a logic error in one of CRMint's retry mechanisms.
Please re-deploy CRMint from dev branch.
Just a follow up on this issue. The client redeployed the CRMint instance with this code change enabled. However, now when they are updating audiences they are getting a 500 error.
I know you mentioned in your last comment that there is a Google Analytics bug that is not fixed for updating certain Google Analytics accounts. Can you share that bug please and is there any way to know whether or not this client is being impacted by that?
I've attached a screenshot. Would you prefer I open up a new issue for this? Thank you!