Integration Statistic
The Rescheduler is a feature available for the following integration types:
- HTTP
- HTTP v2
- MQTT v2
This feature enables automatic rescheduling of uplink message delivery attempts in case of temporary failures.
A new configuration field Retry Schema has been added to supported integrations.
The Retry Schema defines a sequence of retry delays that will be applied if message delivery fails.
By default, the following retry intervals are configured:
- 5 minutes
- 30 minutes
- 1 hour
- Users can define any number of retry intervals
- Retry intervals are applied sequentially
- Each subsequent retry is scheduled relative to the previous retry attempt
With the default configuration:
- First retry → after 5 minutes
- Second retry → 30 minutes after the first retry
- Third retry → 1 hour after the second retry
When a message cannot be delivered to an integration:
- The message is rescheduled according to the Retry Schema
- The system attempts redelivery at each configured interval
- Retries continue until:
- The message is successfully delivered, or
- All retry intervals are exhausted
Retry activity can be monitored in the Integration Retry Statistics tab. To open it Click Show Retry Statistics
- Total rescheduled - Total number of messages scheduled for retry
- Converter stage - Messages rescheduled due to converter-related issues
- Publish stage - Messages rescheduled due to delivery/publishing issues
The Redelivery Window table provides detailed insight into scheduled retries.
-
Redelivery window
Time when the next retry attempt will occur -
Initial retry delay (min)
Retry delay value taken from the Retry Schema -
Stage
Processing stage where the failure occurred:- Converter
- Publish
-
Outstanding count
Number of messages scheduled for retry in this window
PLEASE NOTE ⓘ Statistics are aggregated periodically and may reflect data up to 30 seconds old.
Retry results can be analyzed in the Integration UL Delivery Statistics tab.
To open it click Show Uplink Delivery Statistics
-
If a retry succeeds, the message is recorded as:
- Metric: Dropped
-
If a retry fails, the message is recorded as:
- Metric: Delivered
-
Time window
Time period when the message was processed -
Metric
- Delivered
- Dropped
-
Count
Number of messages
PLEASE NOTE ⓘ Statistics are aggregated periodically and may reflect data up to 30 seconds old.
A new Integration DL Statistics table has been added.
This table displays the number of downlink messages received via integrations.
The Integration Retry Scheduler:
- Improves reliability of message delivery
- Provides flexible retry configuration
- Offers detailed observability through statistics and tables
- Helps diagnose issues at different processing stages