Good day, I’m using the standard integration using nodejs sdk and I’ve been testing my integration which has been going great but then I stumbled upon this error some minutes ago, “er_con_count_error too many connections” and I haven’t come across that error in all my testing.
I noticed the error too a couple of hours ago on my test integration, hence the googling. I went back and tried the good old off/start solution and things are fine now. Test payment went through. But it will be nice for FW to tell us why that may have happened.
To gracefully handle rate limits, the best option is to look out for http response code 429 and implement a graceful retry. The retry mechanism should have a backoff mechanism to ensure the rate limits are again not exceeded.