question

There is more than only your flowitem disappearing. The involved token gets moved, too and as a result the AGV is not acquired anymore. There is something wrong with the internal logic, when you delay an AGV in combination with process flow, because the token in process flow does not know, what happens next if an external event delays the process flow. Obviously the token must be preempted and in an invisible process be delayed. And after finishing this invisible process the token must be reinstated back into the preempted process activity. That is not easy, because there are other interrupting processes like timetables or MTBF/MTTR tools, too.

I inserted a control process to keep track of tokens in the process. I assign colors to tokens and create a copy to push the token reference onto a list. By this I can keep a connection to the parent token. You will see that after returning, they don't apply to the task activity option to wait until complete. The tokens still reach the sink activity. What you have interpreted as a returning of an invisible gone item is infact a new transported item. The transported item is teleported into the destination queue. test_agv_waypoint_delay_Procees_flow_ts.fsm

Hi @Ryosuke S, was my answer helpful? If so, please click the red "Accept" button at the bottom of the answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.