Boundary Timer Event sequence flow is based on associated Probability not the Timer

[Former Member]

I have a Boundary Timer on a task that is set to interrupt (cancel) the task if the duration expires. Signavio adds a Probability (2%) to the sequence flow coming out of the Boundary Timer and it is this Probability that appears to be used to determine when to route the token along that path rather than simply when the timer Duration expires/completes (which in this case should happen if the required Resource, associated with the swimlane, were not available).

screen-shot-2022-11-02-at-24352-am.png

If I set the timer duration to 1 min and the task execution time to 10 minutes, the timer never seems to interrupt/cancel the task (perhaps 2% of the time it would). If I increase the Probability on that outgoing sequence flow, then I see tokens flow though the Boundary Timer - the higher the Probability, the more interruptions occur. This is the case regardless of task type.

Thoughts?

[Former Member]

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with: https://community.sap.com/resources/questions-and-answers, as it provides tips for preparing questions that draw responses from our members.

For example, you can:

- outline what steps you took to find answers (and why they weren't helpful)

- share screenshots of what you've seen/done

- make sure you've applied the appropriate tags

- use a more descriptive subject line

The more details you provide, the more likely it is that members will be able to respond. Feel free to also take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.html

Should you wish, you can revise your question by selecting Actions, then Edit.

By adding a picture to your profile you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html

Questions on how to draw responses from members? Check out this discussion on how to improve questions. https://groups.community.sap.com/t5/welcome-corner-discussions/advice-from-sap-champions-questions-a...

[c_eliescu]

Whether an attached timer event is triggered in the simulation depends solely on the probability specified in the scenario in the simulation. Other input values are not taken into account. The logic that a task is interrupted as soon as the corresponding resource is no longer available cannot be simulated. (Apart from the fact that it should rather be a conditional intermediate event rather than a time intermediate event).

[Armand_Doucette14]

Thank you very much Carmen! If you don't mind a followup...

I agree, it is an inappropriate use of a timer event (I showed students the proper model). So students could simulate the entire model, I suggested they consider that in this situation, if the task was not completed within a short time (the timer duration), then just pass the token to the alternative resource. That said, in a scenario where an intermediate boundary timer event were appropriate, I'm curious why the timer could not be simulated. The simulator considers how long the task takes and will therefore hold the token for the task's execution time - so why can't the attached timer interrupt that task based solely on the timer expiring (rather than based on a probability)? Thanks in advance for any additional insight.