Common causes of errors
Errors when processing messages in the outbound queue occur because there is a problem delivering a message to the endpoint that is specified for the external system. Errors when processing messages in an inbound queue are typically related to a business rule validation or in the inbound processing of the enterprise service.
For outbound processing, typical problems are disruptions of the communication link to the external application, issues with the database table space, or file space issues in the external application. To resolve an outbound error, you typically do not need to modify the XML or JSON message.
The following table describes the most common message errors that you can encounter and provides suggestions for correcting them. Correcting an error in the message can create a mismatch in data between the sending and receiving systems.
Error type | Description | Actions |
---|---|---|
Sequence error | Caused by sequencing problems between messages. The system stops message processing when a record references another record that is in a pending state. | This error is applied to ensure that records process in the correct order. Depending on the direction of the message transaction and the processing logic that applies, the processing can self-correct the error when the record that was in the pending state has processed. |
Data error | Occurs because the data or record does not exist in the system database, and is not part of the inbound messages in the queue. | Add the missing data to the system database. |
Communication error | Caused by communication problems with the external system from system failures or network issues. | Restore communication with the external system. |
Message error | Caused by erroneous message data values. |
|