Error rate up to 17% in 24 hours. I’m not sure if it’s caused by a system problem.
17% is definitely a very high number of errors, but I don’t really see this in my logs…
I have just applied changes so now these errors throw 503 instead of 422 so you are not charged for these occasional issues (which happen rarely). While there are smart retries and proxy rotation implemented under the hood of this API, it is not possible to provide 100% success rate, this is scraping ? just retry in case you get bad response. Good luck!
加入讨论 - 在下面添加评论：