In the documentation, there is no mention indicating that this type of modeling is unsupported.
Attaching 2 intermediate timer boundary events with the receive task also doesn’t seem feasible.
Given the requirement to include two intermediate timer events and one Receive Task, could you suggest an alternative implementation to achieve this functionality?
Since attaching a Receive Task to an Event-Based Gateway is not allowed, I attempted to achieve similar functionality by attaching two interrupting timer boundary events (T1 and T2) to the Receive Task. However, during token simulation with this setup, only the T1 timer was triggered, even when T2 was selected.
Additionally, I was concerned that using two timer boundary events might introduce ambiguity in the process. As a result, I concluded that this approach “doesn’t seem feasible” and began exploring alternative solutions.
As I mentioned earlier, there seemed to be an issue with the token simulator, which initially led me to switch to an approach using an Event-Based Gateway. However, after deployment, I observed that both timer events are being triggered correctly based on the configured times.
Given this, I will proceed with the design of using a Receive Task with two interrupting timer boundary events.
