The next figure illustrates how to position Schedule Timeout and Cancel Timeout blocks to limit the time on a linear entity path. The linear path has exactly one initial block and one final block. A Schedule Timeout block precedes the initial block (LIFO Queue) on the designated entity path, while a Cancel Timeout block follows the final block (Single Server) on the designated entity path.
In this example, the Cancel Timeout block is optional because it is connected to the Entity Sink block, which has no entity output ports. However, you might want to include the Cancel Timeout block in your own models for clarity or for its optional output signals.
Other examples of timeouts on linear entity paths include these:
In the example below, entities from two sources have limited lifespans. Entities from a third source do not have limited lifespans.
Note: When the Replicate block replicates an entity subject to a timeout, all departing entities share the same expiration time; that is, the timeout events corresponding to all departing entities share the same scheduled event time.
In the example below, entities have limited total time in a queue, whether they travel directly from there to the server or loop back to the end of the queue one or more times.