Sending a message multiple times after a specified start time

Aim

Use TimeoutControl and TimeoutNotification nodes to send a message into a message flow at 17:00 hours and then send the message again every 5 minutes until the message has been sent 10 times.

Description of the flow

The diagram shows a timeout request message, and some of the values contained in the message, passing through a TimeoutControl. There is also a TimeoutNotification node with the same identifier as the TimeoutControl node. A description of the diagram is given in the text.

The diagram shows the path of a message that contains a timeout request through a TimeoutControl node. A TimeoutNotification node with an identifier matching the TimeoutControl node then processes the timeout request. The diagram also shows the message that he TimeoutNotification node produces after processing the timeout request.

The message comes into the TimeoutControl node with the following values set in the timeout request section of the message:
  • Action set to SET
  • Start Time set to 17:00
  • Interval set to 300
  • Count set to 10

The TimeoutControl node validates the timeout request; default values are assumed for properties that are not explicitly defined. The original message is then sent on to the next node in the message flow. If the request is valid, the TimeoutNotification node with the same Unique identifier as the TimeoutControl node propagates a copy of the message to the message flow at 17:00. The message is sent again after an interval of 300 seconds, at 17:05. and every 300 seconds until the message has been sent 10 times, as the Count value in the timeout request specifies.

See the Timeout Processing sample sample for further details on constructing this type of message flow.

Related concepts
Handling TimeoutNotification errors
Related reference
Sending a message after a timed interval
Automatically generating messages to drive a flow
TimeoutControl node
TimeoutNotification node
Timeout request message