Show TOC

Processing StatusLocate this document in the navigation structure

During message processing , each message passes through multiple statuses. These statuses are represented by a corresponding icon in the Status or Acknowledgment Status column in the list of processed XML messages .

Further information: Monitor for Processed XML Messages

  • If you have not determined any versions of the message, the system displays the overall processing status of the message. This corresponds to the status following the last processing step executed.
  • If you have already determined the versions of the message, the system displays the status of the respective processing step.

Explanation of the Different Statuses

The following statuses refer to processed messages.

Final statuses when processing synchronous and asynchronous messages

Status Meaning

Message processed

This might only apply for the current system for asynchronous processing.

Message already processed

A message with this message ID already exists in the receiver system. Processing is therefore completed for the sender system.

Messages with errors canceled

Processing of a message with errors was canceled. The message can then be deleted with the next delete job.

Message scheduled (commit missing)

The message has already been scheduled but has not yet been released for processing.

Branch: Multiple receivers found

Multiple receivers were found, therefore the message is branched. Message processing is complete for this message. The new messages that are created by branching are processed further.

Error statuses when processing synchronous and asynchronous messages

Status Meaning

System error (restart possible)

A system error occurred during message processing. In synchronous processing the error is returned to the sender.

Application error (restart possible)

An application error occurred during message processing. For asynchronous processing, this status only occurs in the receiver system, for synchronous processing, it occurs in all systems involved.

No receiver found

No receivers were found. Message processing is therefore complete for this message.

Intermediate statuses when processing synchronous messages

Status Meaning

Message scheduled (commit follows)

The inbound message is scheduled and released for processing.

Scheduled for outbound processing

Receiver determination is complete. Exactly one receiver was identified and the message was scheduled for further processing.

Message is in automatic retry mode

There was an automatic restart following errors in the HTTP connection.

Manual restart for version

The message has been rescheduled. This is the status of the message when you restart a particular message version manually.

Message changed manually

A message with errors was corrected manually and saved.

Acknowledgment message stopped

The acknowledgment message was stopped.

Message transferred to Process Engine

The message was transferred to the Process Engine for further processing.

Log version

This message version was generated by logging and does not have a particular status.

Statuses for acknowledgments of asynchronous messages

Status Meaning

Still awaiting acknowledgment

No acknowledgment message has arrived yet.

No errors in acknowledgment

The message was received by the receiver without errors and was processed successfully by the application.

Acknowledgment contains errors

Message processing contained errors and the acknowledgment message contains a system or application error.

Branch: Multiple receivers found

Multiple receivers were found during logical routing. Therefore, the acknowledgment message is branched. Processing is complete for this acknowledgment message. The new acknowledgment messages that are created by branching are processed further.

Corresponding message was canceled

Processing of the corresponding message was canceled and it can now be deleted.

Acknowledgment not possible

The acknowledgment message cannot be sent.

The Acknowledgment Status column displays the status of acknowledgment messages.