The collection expiry is a property on the Collector node to set a maximum timeout for adding messages to a message collection.
Before you start:
To complete this task, you must have completed the following tasks:
When messages are added to a message collection, the incomplete message collection is stored on a queue. If the message collection's event handlers are not satisfied, then the incomplete message collection is stored on the queue indefinitely, and not propagated for further processing. You must configure a timeout value for a message collection to ensure that messages do not get added to a message collection indefinitely. You can configure this timeout, as a value in seconds, in the Collection Expiry property on the Collector node. The collection expiry timeout starts when the first message is accepted into a message collection. The collection expiry overrides any individual event handler timers. When the collection expiry timeout has passed for a message collection, the incomplete message collection is propagated to the Expire terminal. Connect appropriate processing nodes to the Expire terminal, to handle any expired message collections in your message flow.
To configure a collection expiry: