Hello,
I believe I've found a bug related to resource seize/release/packing/unpacking. I'm trying to model a process that the operator works on a batch and does the same activity to each piece of the batch individually before moving onto the next activity to do for all the batch individually.
Problem: Once the resource reaches the release action after pack or unpack it sends the resource back to the first Packing activity instead of the Resource Pool.
The text below the resource pool indicates the location the resource is currently at.
I've tried unpack on both sides of the resource release to no avail. Additionally tried adding a threshold trigger with Seize to not allow the step before to proceed if no resources were available.
My work around for now is to just multiply the process time by the batch size.
Attached is the model.
Best Regards,
Brandon Holle