I am a contributor to and heavy user of the testrail-python bindings, and have noticed an uptick in 503 (“Service Unavailable”) responses from the TestRail API. Anecdotally it seems as if they have become more common over the last ~month or so. I have added code to automatically handle and retry these 503 responses, but even with multiple retries, delays, and back off I will still ultimately get a 503.
Given that, I have two questions:
- Is Gurock aware of an uptick in 503 responses?
- Is there a recommended way to handle these? Perhaps a recommended amount of time to wait for the service to become available? The API documentation is fairly vague: (“Applications and libraries that use TestRail’s API are responsible for handling 5xx errors and are supposed to retry requests later in this case.”)