Error handling

Implement a catch-and-retry for 50x or 429 (throttling) errors from the API, with an exponential back-off retry interval.

This increases the reliability of the integration. Occasionally, the API can experience load spikes that require additional system resources.

The back end is designed to scale up when these are detected. However, there may be a delay before these capacities are available.

Handling Probation alert (Webhook Permanent Probation Handling)

1. The alert routes to connectors@lionbridge.com(onnectors@lionbridge.com) and a support ticket is created automatically,
2. Connector support identifies client based on alert message and checks for the cause.
3. Connector support contacts the client via ticket/email.
4. (Optional) Client acknowledges and confirms endpoint is restored.
5. Connector support restores the webhook. Currently, the client can restore themselves using the PATCH Listener method which will automatically pull the listener out of probation. Note: Job uri and Asset tasks uri are required to re-enable the listener.
6. At this point, there are a few options: a. the translation operations team/connector support redelivers the stuck job(s); OR b. the client connector invokes retries on failed payloads; OR c. the client connector retrieves translated content through built-in overrides, if available.