Issue with API rate limit and connection error while querying the API in local development.

I got a single error while querying the API

API rate limit exceeded

. Since then, I’m getting

ECONNREFUSED 34.102.211.197:443

.
The project usage seems well within its limits, and I’m not getting the error if I change to another network connection.

Could it be that my IP has been blocked? Is there anyone here who can help me to figure this out?

It seems to be working again. I’m still curious to find out what it could have been, for next time.

can you please check that your API is getting called in a loop i faced same issue check in console.

Thanks User. There is quite a bit of outgoing requests, but no infinite loops, if that’s what you mean?

It worked for a while, but now I get the same error again. Hmm…

Now I’m getting …

And now it’s working again… Strange

can you send me the console pic.

Hey User! What's the context that you're getting this error in?

Hi . I’m getting these errors in local development while building – using a custom static site generator. There are about 600 queries, but I’m caching them to disk, so they are requested only once in a while whenever I manually empty the cache. Of course, then all of them will be requested in one burst.

Hi . I’m getting this in local development while building using a custom static site generator. There are about 600 queries, but I’m caching them to disk, so they are requested only once in a while whenever I manually empty the cache. Of course, then all of them will be requested in one burst.

Hi . I’m getting these errors in local development when building a website using a custom Node.js static site generator. It uses

@sanity/client

.
There are about 600 queries, but I’m caching the results to disk, so they are requested only once in a while whenever I manually empty the cache. But of course, then all of them will be requested in one burst.

I’m usually not using the CDN in development, relying on the local on-disk cache I put between.

I’m usually not using the CDN in development.

Ah, got it. I think you're hitting this rate limit for concurrent queries, which is why you're only occasionally getting the error.

That must be it . Thank you very much!

Does the

@sanity/client

have the option or possibility to rate limit itself?

Is there any way to limit concurrency in the

@sanity/client

?

There isn't a method built into the client, but there's an example of handling concurrency in this bit of the docs . You could probably adapt it to suit your needs here!