Daniele Borgna

Additionally, also with your model I have a stuck situation with 99 Analyzed samples instead of keeping until 1000000 or convergence because some jobs are not triggering the join on their second iteration.

It is similar but J1.1 does not spawn from the J1Source. I attach my model..

Hello. I'm working with a Guard policy in a join and created a simple example to replicate the error I encountered. I have one closed class, J1, generated in the J1 Source. This job is forked into two sub-jobs of the same class. Then, one of the jobs is sent to the Class Switch and becomes J1.1. In the Join node, the policy used for the J1 class (the parent job class) is Guard, with 1 job for J1.1 and 0 for J1. This should mean that when the J1.1 job is received at the join, the J1 job is unlocked...

Guard policy of a Join not working