State Model Timeouts and State Timeouts

You can define timeouts at the state model level and for each of its states, except for the start, end, and Call State Model nodes.

For the state machine, the timeout value specifies how long the state machine should wait before it completes. A timeout has an expression and an action. Both the expression and the action are defined using the TIBCO BusinessEvents rules language. See Defining Timeouts for complete details.

• The Timeout Period
  A timeout expression specifies how long the state machine (or state) waits before it completes.
• State Timeout Scheduler Controls
  The refreshAhead and pollInterval properties controls the internal scheduler that manages state and state model timeouts.
• Runtime Behavior
  At runtime, a state machine timeout timer starts when the state machine starts. The timer is cancelled when the state machine completes.
• Multiple Pending Timeouts
  A state machine can have multiple pending timeouts. When the state machine exits an enclosing state, it exits all the enclosed states too. So if the result of a composite state timeout is to exit the state, then the state machine cancels all the enclosed timeouts (if any).
• State Timeout - Next State Choices
  You can configure the Timeout Action setting for a state, which determines what state to go to next in the event of a state timeout.
• Locking (and Loading) in Timeouts
  When TIBCO BusinessEvents uses Cache OM in a multi-agent or concurrent RTC application, locking must be used to ensure data integrity. When cache-only cache mode is used, you must also load concepts as needed.