Abort a use operator for Process

This is a question from Sung Kim:
"Hi,
Could you please advize me how to cancel the "waiting operator"? I have one multiprocessor currently waiting a operator to process one of the sub-processes. However, I would like to bypass all the processes if the flowitem waits for the operator too long. I tried "moveobject" and "destroyobjectevent" for the flowitem. It successfully move the flowitem out of the Multiprocessor (bypass), but the MultiProcessor state is still "waiting the operator" and yellow box is surrounded. Consequently, the next new flowitme for the Multiprocessor cannot get into the MultiProcessor. Any suggestion?

Thanks,
Sung"

This question is basically asking how to abort the use operator for process if the flowitem waits to long. One question I have for you Sung, What are you doing with the flowitem? Are you processing it without the operator or something else?

Brandon

Sung Kim,

Attached is a model that shows how to do what you are trying to do by searching through the task sequence queues of the dispatcher and operator(s). If it finds the task to come be utilized, then it destroys that task, destroys the events of the multiprocessor, resumes the multiprocessor, and releases the item.

The main code is in the OnMessage trigger of the MessageHandler object. The Multiprocessor sends a delayed message to the MessageHandler from the Pick Operator trigger.

This works well in this little sample, but if your object/model gets more complicated than this little sample model shows, then you could get into big trouble fast by messing with the standard object functionality using the destroyeventsofobject() command.

You may instead want to use a BasicFR to get more control over exactly what happens to the object using the receiveitem() and releaseitem() commands. The logic would be similar, but then you wouldn't have to bypass the regular multiprocessor logic by destroying its events. This is less likely to give you trouble in the long run when you try to implement this sort of logic in a bigger model.

Thank you much, Phil and Brandon.

I understand that description of my issue might be odd to you. I admit that the description doesn't show the whole picture. For the answer Brandon's question, when the flowitem waits for the operator too long, basically, it cancels the all subprocesses in the multiprocssesor and eventually move to other station and do the rest of processes with other temp operator. It is not exactly but similar to balk in a queue situation.

Phil, thank you for the explanation and the model. It is very good to know about the MultiProcessor's nature. I will study your model soon. While I learn your logic, I will let you know if there is an issue.

Thank you very much for your time and help.