Maybe I'm still misunderstanding the tagged resource, but I ran into the following problem:
I'd like to get an operator from a dispatcher team to guide an item through a number of successive objects, say Queue1 -> Queue2 -> Queue3. I thought I should use a Tagged Resource to make sure the dispatcher doesn't snatch the operator away as soon as an item is unloaded.
However, if the operator arrives with an item at Queue2, and Queue3 is empty, then Queue2 immediately tries to send the item on while in the operator's Unload task. Since the operator is technically still busy, the task sequence for the transport to Queue3 is stored away somewhere on the flow item, the flow item lands in Queue2, and then sits there. Somehow the stored task sequence never makes it back to the operator to be executed.
Please see the attached model for a demo. I can get it to work, by closing the queue's output in the on entry trigger, then re-opening it with a delay of zero, but it feels like the standard pick option is designed precisely so that I don't have to think about that.
