How we will attempt to send your system when it fails.
This policy may changeOur failure rate has been fairly low so far and this policy is safely supported, but if a high volume of failures begins to happen we may reduce our total duration to address volume issues.
Redrive policies come into effect when your system fails to respond in accordance with our expectations for assuring 'delivery' to your system. Specifically, a 200-399 range status code and responding within 5 seconds.
Our current policy is to retry within seconds, after the first failure. Thereafter, for each attempt a delay is calculated based on the number of attempts being multiplied by 5 (in minutes). So the re-attempt could take between 5 minutes and about 102 hours (a little over 4 days total time). This should give your system plenty of time to recover. Subscriptions will be disabled when any event hits 50 failed attempts. Use the Disable Callback to be notified when this happens.
If you would like your Subscriptions to never be disabled, you can update attempts to 3 or less. Once you do that you can then pass auto-disable: false. We will then only retry delivery 3 times (in accordance with the above policy), but we will never disable your Subscription.
Disable Callback
Any time a Subscription is disabled the disableCallbackURL will be invoked with a GET request. This get request will add a timestamp and the id of the Subscription via query string parameters. You can add your own query string parameters as well and it will be properly amended with id and timestamp values in addition to these static values provided in the URL.