To avoid sending duplicate events to the destination application, you may want to prevent a recovery from automatically resubmitting all service calls that were in transit when a failure occurred. Before the server failure, you can configure a nontransactional collaboration to persist any service call event in the In-Transit state when a failure and recovery occurs. When InterChange Server Express recovers, the service call events remain in the In-Transit state, and you can use Flow Manager or Failed Event Manager to examine individual failed events and control when (or if) they are resubmitted.
To configure a collaboration to persist a failed service call in-Transit state, go to System Manager and select the Persist Service Call In Transit State check box in the Collaboration General Properties window.