Retry Processing

ERP Connectivity allows to retry the message processing manually and automatically.

Manual retry of message processing is performed via the retry option in the Message Logs and Orchestrator Logs web pages.

Automatic retry of message processing is performed via package configuration. The default retry behavior and the retry behavior for specific external error codes can be configured using the below settings.

Default Retry Processing

Sets the default retry behavior.

RetryLimit

Maximum number of automatic retries for a message processing.
DefaultRetryInterval

Default wait time between retries (can be overridden per error code).

Error Specific Retry Processing

Overrides the default retry behavior for specific error codes (e.g., only retry on timeouts, or use a different interval for certain errors). A collection of error codes can be specified with specific retry behavior for each error code.

ExternalCode

The error code from the external system (e.g., ERP error code).
Retry

Indicator to automatically retry on this error code or not.
RetryInterval

Wait time between retries (overrides the default retry interval for this error code).

Response Path Retry Processing

When a package execution completes, the result is published according to the configured Response Path. It supports different response path types, such as IAS notifications, payloads, and connector-based responses.

IasNotificationResponsePath

Publishes notification messages to IAS via AMQP.
IasPayloadResponsePath

Publishes the final result object as a payload to IAS.
ConnectorPayloadResponsePath

Publishes the result payload via a configured connector.

Response Path retry is performed via package configuration.

RetryLimit

Maximum number of automatic retries for publishing the result.
RetryInterval

Wait time between retries.