Not really...I submit a ticket to the support team already, still waiting for the response...
We probably get a response like that because we are being limited behind the scenes. I imagine that the service is restricting the amount of incoming requests per second, when we receive this error.
Commonly restrictions like this are based on restricting traffic generated on 1 IP.
I would look at the time taken, if you notice that as the traffic increases, the time taken increases drastically, and then the error in responses.
The ticket is a good idea to start, I would still look at distributing load through agents (multiple IP's) to see if that resolves it.
Got it, I will try to run on agents to see the results, Thanks!!
