search

m-wrzr / populartimes

MIT License
815 stars 167 forks source link

Exceeded query limit reply, but Google console #70

Closed mick-net closed 2 years ago

mick-net commented 5 years ago

When using the Populartimes populartimes.get function I am getting a "You exceeded your Query Limit for Google Places API Web Service, check https://developers.google.com/places/web-service/usage to upgrade your quota." (Small area's work before getting the API error.

When checking the usage on the Google Developers Console, I don't see any quota exceeding it's limit. (see picture: https://imgur.com/a/eoBG9zB )

Could it be that the amount of threads/ workers is set too high (Eventhough the request per seconds limit has not reached yet according to Google)? What is the best way to limit the requests per second/ limit the threads in the crawler?

I guess this post is old (old quota's and limits), but maybe related? https://stackoverflow.com/questions/14014074/google-maps-api-over-query-limit-per-second-limit

JosiahParry commented 5 years ago

@vermaat this is probably because google requires you to fill out billing information regardless of if you have or have not reached the quota.

mick-net commented 5 years ago

Hi JoshiahParry,

Thanks for the reply. I have my bank account connected to the API. As you can see in the image (https://imgur.com/a/eoBG9zB ) I am not even close to the set limits.

tejasavkhattar commented 4 years ago

@vermaat Where you able to find any possible solution to this problem?