🔄 New feature: HTTP request backlog

The HTTP Request Backlog ensures that failed HTTP requests in message routing are not lost.
Instead, they are automatically retried and, if necessary, stored for later processing.

🧩 What Does This Feature Do?

When the backlog is enabled and an HTTP request is defined in a routing rule:

• If the target server does not respond with HTTP status 200 (OK), the request is automatically retried.

• If the second attempt also fails, the request is stored in a backlog table.

• If the "Process HTTP Request Backlog" option is active, a background process will regularly fetch and re-execute all pending requests from the backlog until they are successfully processed (HTTP 200).

✅ What Needs to Be Enabled?

To make this feature work, both of the following options must be enabled:

• ✅ Enable Backlog

• ✅ Process HTTP Request Backlog

You can find both options in the web interface under:

Web Interface → Configuration → Message Routing

📅 When Does the Feature Apply?

The feature only applies when a routing rule contains an HTTP request.
It works with:

• Incoming SMS

• Incoming Emails

⚠️ It does not apply to other rule types.

🧪 How to Test the Feature

To test the feature:

1. Send an HTTP request to an unreachable or non-responsive server

2. Check the logs:

   • You’ll see an initial retry attempt

   • Then, the failed request is logged into the backlog table

3. View the backlog table here:

   🔗 https://<server>/?modul=maintainance&site=cleanup

🧼 View and Clean Up the Backlog

Stored HTTP requests can be viewed and deleted at:

🔗 https://<server>/?modul=maintainance&site=cleanup

🚫 Deactivation

To disable the feature:

• Uncheck "Enable Backlog" to stop storing failed requests

• Uncheck "Process HTTP Request Backlog" to stop automatic processing
  → New failed requests will still be stored but no longer retried

For further assistance or if you have any questions, our customer service team is happy to help.