During the simulation run the following message is received:
A resource was captured using a Get or JointlyGet statement but not Free’d before exiting. The entity left the system with a resource still attached. The engine recognizes this as an error because the model will soon run out of resources and not be able to function.
The problem is easy to find using a process of elimination. Place a FREE ALL at all exit points of the model, then remove the statements one by one until offending activity(s) can be determined. Follow the chain of activities backward until it can be determined why a resource was captured without a corresponding Free.
If you need further help, please contact support.