About Join Timeouts
For most step types, a join timeout can be defined as a static value or dynamic value. A static value is a specific time duration that you define when you design the process model. At run time, the timeout value is applied as defined, and cannot be varied unless you update the process model.
Join timeout on a Intermediate catch message event step, or any join step, starts as soon as either the inbound transition or the document arrives. If the timeout depends on a pipeline variable, you should make sure the process model is designed so that the variable is populated on either of the transitions.
You can also configure a join timeout to use dynamic timeouts that are determined at run time. Dynamic step timeouts apply to AND and COMPLEX join types. You can configure dynamic timeouts in the following ways:
By specifying a pipeline field value. This enables you to dynamically set the timeout value at run time.
By specifying a value based on a business calendar. This enables you to count only business days and business hours when calculating the timeout duration. Although the defined timeout period is fixed, the calendar duration of the timeout can vary, depending on presence or absence of working days and non-working days. You can also specify a pipeline field value to use with a business calendar, to provide a true dynamic timeout value.
For more information about setting join timeout values, see
Defining a Join Timeout.
Related Topics