pub.publish:getRedeliveryCount

The redelivery count indicates the number of times the document has been redelivered to the trigger queue on the Integration Server. A document is redelivered to a trigger queue if the Integration Server shuts down before processing and acknowledging the document.

redeliveryCount	String Specifies the number of times the trigger on Integration Server has received the document. The redelivery count can be one of the following:
	A value of...	Indicates...
	-1	The transport used to send the document does not maintain a document redelivery count. For example, a document received from a webMethods Broker version 6.0.1 has a redelivery count of -1. (webMethods Brokers that are version 6.0.1 or earlier do not maintain document redelivery counts.) Integration Server may or may not have received the document before.
	0	The document has been received only once.
	> 0	The number of times document has been redelivered.

If you do not want to use the exactly once processing capabilities, you can invoke the pub.publish:getRedeliveryCount service within your trigger service. The redelivery count for a document can provide an initial indication of whether the trigger has already processed the document.

Integration Server retrieves the redelivery count for the document currently maintained in the invoke state. That is, Integration Server retrieves the redelivery count for the document that caused the trigger service to execute.

When a trigger service satisfied by an All (AND) join condition invokes pub.publish:getRedliveryCount, the pub.publish:getRedeliveryCount service returns the redelivery count for the last document received by the join. For example, suppose that documents A and B satisfied an All (AND) join condition. If the Integration Server receives document A first and document B second, when pub.publish:getRedliveryCount executes, it retrieves the redelivery count for document B.