Testing the API locally and seems like every other call is returning either 503 or 504. How is this reliable? My company is building a feature that we are planning to go to production with, and in this state, I’m honestly not sure if we can. Please help! We are on the pay-go tier 2 plan. Almost feel like we are being routed through a free API; a paid plan shouldn’t be this unreliable.
Hello @Keith_W ,
503 errors are due to our services being temporarily overloaded. Please see this pinned post for suggestions on how to handle this.
@Pooja_Kapse the backoffs doesn’t solve it (whats suggested in pinned post) and its been going on for almost a week now. Also, I’v tried with fresh API keys and no luck. Please see other posts I’v linked below. This is unacceptable for a paid service.
@Logan_Kilpatrick can you please look into this? Support is just telling us to do retries but that doesn’t work as we are constantly getting 503 and 504s. We also don’t have the luxury of waiting for the request to go through with repeated retries/backoffs as the features we are building are customer facing which requires quick responses. This is honestly unacceptable for a paid product.