Model 10 - Attached Error Event
How-to
In this model we introduce the error event. "Task 1" defines a variable, on which the decision making at the branching exclusive gateway is based on. If the variable’s value leads to the error end event, it will fire the receiving error event attached to "Task 3". This event is interrupting and causes the process to proceed to the task "Task Handle Error". If the branching exclusive gateway’s default sequence flow is being followed, "Task 3" will be executed normally.
Approach
-
Define a stochastic variable called x with a Discrete Uniform Distribution with
-
A minimum value of 2
-
A maximum value of 5
-
-
At the branching exclusive gateway set these conditions for the edges:
-
Upper edge:
x <= 3
-
Lower edge:
default
-
| The other event types can be used in a similar way. |
| Some event types have interrupting and non-interrupting properties, others may be used only in an interrupting way (e.g. the Error Event). In case of an inaccurate usage the simulation will throw an error in the simulation report. |
Report
See below for the run configuration, which we set up to receive the report statistics from below.
Please refer to the section Experiment Results for more information on the report specific data.
Run configuration
-
Stochastic Seed: 12345
-
Simulation start date: 1/1/2014 12:00:00 a.m.
-
Simulation stop time: 240
-
Simulation stop time unit: Hours
Report statistics
-
First have a look at the gateway details from Figure 5
-
Our gateway fired the top sequence flow leading to the error sending end event 115 times
-
Which means that "Task 3" has been interrupted 115 times (take a look at the event counter from Figure 4)
-
So, the task "Task Handle Error" has also been reached 115 times (it was only completed 114 times, Figure 3)
-
-
The fact, that the "Task Handle Error" is being executed, has an impact on the process cycle time (see Figure 2)
