422 error RATE_LIMIT_EXCEEDED

Hi,

Received this API error response recently:

422 - Unprocessable Entity - { "error": { "type": "RATE_LIMIT_EXCEEDED", "message": "Rate limit exceeded. Try again later." } }

I thought response code 429 was reserved for rate limit errors and so implemented retry logic for that response code only. I know 422 can also mean other things, like leaving a required field out of an update/create request.

What are the situations where a rate limit error can result in a 422 code? How should I gracefully deal with these errors? I know a caching proxy is recommended but that only works where requests originate from the same process, so retry logic is important.

Peter Novosel any advice appreciated!

2 replies