For asynchronous service operations, the Service Operations Monitor displays different statuses as service operations progress through the system. The typical status progression for asynchronous service operations is:
New -> Started -> Working -> Done
However, you will find messages in a lot different statuses. Here is brief description of each asynchronous service operations.
The item has been canceled. The system cannot process the item until you resubmit it.
This status indicates different outcomes, depending on the type of process that you are monitoring.
For operation instances this status indicates that the operation instance has completed processing and that the publication or subscription contracts have been created.
For publication contracts this status indicates that publication contract was successfully sent to the external system. This can include publications sent using guaranteed or best effort delivery.
For subscription contracts the status indicates that the subscription notification processed successfully.
This status appears for publication contracts sent in Best Effort delivery mode and indicates that the publication
contact was successfully sent, but no acknowledgement was received.
The publication data for the item has been edited. Processing does not resume until you resubmit the item.
An error occurred during processing. Manual intervention is required.
This field is used in conjunction with message segmentation and future-dated publications.
The status of a segmented message is Hold while the system is processing the segments in the message. The status of a future-dated publication is Hold until the date and time specified to process the publication is reached.
Either the item has been written to the database but has not been dispatched yet, or the item has just been resubmitted.
The system encountered an intermittent error during processing. The system retries service operations with this status automatically.
The dispatcher is in the process of passing the item to a handler, but the handler has not received it yet.
This status indicates that a process schedule instance has been created for the transaction.
The system has reached the maximum retry count to send a service operation.
The handler has accepted the item and is currently processing it.