Why when returning a token for the travel activity, after a preemption block, the task executer doesn't continue the traveling task from where it left off? The task executer's state returns as idle, instead of traveling empty, as if it had already finished the activity.
And he only starts moving again after a travel activity with another final destination.
Is this some incompatibility between task sequences and preemptions activities?Test_TaskExecuter.fsm
Hi @Beatriz Spaggiari, was Joerg Vogel's answer helpful? If so, please click the "Accept" button at the bottom of their 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.
There is not a inconsistency. If you call preempt on a taskexecuter traveling on a node network, you set him directly into an offset travel state. This behavior is default. Now you assume that there is a incompatibility by using process flow preempt and restore action, but you observe only a behavior totally independent from process flow.
15 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
