Exception error for TaskExecuter: :onTimerEvent - sends 2 ops to processor?

[jake_w]

[ FlexSim 19.0.4 ]

I am trying to add an operator and a process to this model -> cut-process-j.fsm and it works as it should until time 954.86135 when I get "Exception Caught in TaskExecuter::onTimerEvent(treenode involved, int code, char *datastr) object: /Operator1" which is exactly the same as the error in this question: https://answers.flexsim.com/questions/71257/using-destroy-or-moveobject-commands-will-leave-ev.html

I tried adding a custom code with the destroyeventsofobject() logic before the Move Object in the process flow, but that did not fix the problem. Is there another place I need to insert that logic?

This is the model with the error -> cut-process shaping.fsm

[Brandon_Peterson · Accepted solution]

@Jake W

The problem you are having is a result of how you are creating and dispatching the task sequence in your process flow. In the "Create TS" activity you need to clear the "Task Executer / Dispatcher" option by hitting the red 'x' icon next to it. This option causes the tasksequence to be "dispatched" to that taskexecuter. So, when you get to the "Dispatch TS" activity later it is effectively dispatching the task sequence for a second time. This second dispatch is what is eventually causing your problem.

On a side note: the reference to the item in the "Load From Pallet" and "Unload at Cut" activities are both referring to the same object but use different ways to reference it. They both work but it may not in the future if you make certain changes.

I hope this gets you back on your feet, Brandon

P.S. I was looking at the "cut-prcessshaping.fsm" model.

[jake_w]

@Brandon Peterson

Yes this was a huge help. Thank you.