MM-Detection-Delayed-Retry

The principle behind the "retry" option is that, if the event that should have occurred before this one has not yet arrived, IBM® Business Monitor will delay processing this one for a while before trying it again. During the requested delay, other events that have not occurred will have a chance to arrive and be processed.

Each event has the potential of being analyzed by the monitor model application depending on how the model is written. If an event is determined to be early (implying that a prerequisite event has not yet been processed by the monitor model application), the event is returned to the event stream moderator and held for an amount of time (delayed), and then resubmitted to the monitor model application (retried). You can configure the number of times that the event is retried. After the specified number of retries, the event stream is shunted to the error queue.

To use this feature, include qualifications in your correlation expression (specified in the inbound event in the Monitor Model editor) that cause it to fail correlation if something that an earlier event would have set has not yet been set. For example, you might change the correlation expression

orderID = OrderEvent/extendedData/orderID

orderID = OrderEvent/extendedData/orderID and fn:exists(orderAmount)

In this case, if the earlier event that sets the orderAmount has not yet been processed, this event will not be processed either.