When a remote is set up, you have to decide a retry policy in case the HTTP notification does not reach your server.

Retry policy will be triggered when your server is not processing the HTTP notification correctly. It means that your response to the HTTP notification is anything else than an HTTP 2XX.

Retry policy can be set to none, bounded or always, but in any case the maximum period of retry for a notification message is 3 days.

Available Policies #

Retry policy is applied if your server is not responding HTTP code 2XX (for example, another HTTP code or a time-out) to a notification send by the remote.

In this case the notification message will be stored & we will try to send it againg based on the retryPolicy decided for this remote.

Be careful: retry policy is not made for data storage use! It is a remedial tool used to help when a service failure (on your side). It has a limited tolerance for unavailability and therefore a limited storage depth.

None & Bounded

"retryPolicy": {
    "policy": "None"
    }

"retryPolicy": {
    "policy": "Bounded"
    }

When the retry policy is set to None or Bounded, if the HTTP notification is not received on your side, the message will be sent again:

• None: only one single retry.
• Bounded: with a limited number of retries set with retryNumber & retryDelay for a maximum of 3 days.

Maximum of 3 Days #

We can not store your messages forever, because doing so, it would be very likely that the remote service would undergo slowdown when too many messages are enqueued.

In case your retry policy is set to Bounded our server will try to send you the HTTP notification for a maximum of 3 days at the frequency set in retryDelay.

After these 3 days of retry we will stop sending and storing this notification message.

After the first message not processed on your side, other notification messages being triggered in this monitor will also continue to be sent during 3 days after the moment they were triggered.

However, after 3 days, it’s still possible to retrieve data using the REST API within the normal period of 2 months.

Info: The retry policy impact the notification message, not the callback. Others remote related to a callback are not affected by the retry policy. It means also that your server needs to respond a 2XX to a message send for this particular remote in order to get out of the retry policy.

Enter in Retry Policy #

When an event failed to be processed by your server, the retry policy process will be triggered.

The event HTTP notification is stored in our database, and we will try to send it again according to your policy.

Get Out of Retry Policy #

To get out of retry policy your server needs to respond a 2XX to any new HTTP notification of this remote.

Once an event is triggered, or on frequency based on your retryDelay, a message is sent to your server.

If your server respond a 2XX, your remote is removed from retry policy and all stored HTTP notifications are sent.