Webhook Callback Failure

We have implemented a callback retry mechanism in our application to ensure reliable communication between our system and your application. This mechanism is designed to handle temporary failures by automatically resending the callback at predetermined intervals.

When a callback is made to your application, our system checks the response to determine the outcome. A response status code 200 to 299 indicates a successful callback. Any status code outside of this range is considered a failure and triggers our retry mechanism.

The retry mechanism is as follows:

1. Initial Attempt: When our system sends a callback and it fails (status code is not 2xx), it will automatically schedule a retry.

2. Retries: The system will make several retry attempts. Each subsequent retry is spaced out at increasing intervals, allowing for a balance between resolving temporary issues promptly and conserving resources for more persistent problems.

3. Failure Handling: If, after all the scheduled retry attempts, the callback continues to fail (i.e., a non-2xx status code is consistently returned), the system will cease further retries.

This strategy ensures that short-term network issues or other temporary problems are effectively mitigated, providing a resilient mechanism for maintaining the flow of data. We encourage you to monitor the status of callbacks and reach out to us if you notice an unusual pattern of failures, ensuring any underlying issues are addressed promptly.