Subflows: operator´s task stuck when rull all at a time with task sequences.

Question

question

Santiago Serrano asked Feb 12, '24 Jason Lightfoot commented Feb 14, '24

Subflows: operator´s task stuck when rull all at a time with task sequences.

Hi All.

when I try to create simple or complicated Tasksequence in subflows the operator gets stuck in one of the tasks and I don't understand the reason to fix it, especially large models.

If you run each task separately from the subflow, executing each task as "Run tokens one at a time" it has no problems, but if you run them all at the same time and separate each task as a "task sequence" so that they remain in the queue of tasks of the operator, it gets stuck in some of them.

I would like to know how to fix the error, because I need the way I assign tasks and priorities (for models with many tasks) can be done this way, since I am controlling almost everything through the task queue.

I attached a picture of a simple model of moving boxes from one queue to another, each task is moving a box. I ran the example sending the same task 10 times. In the first case with one token at a time, it moves them all. But in the second case that only change the token to run them all at the same time, the operator is stuck in one of the tasks, in this case in the unload, but does not even want to do the load.

This error or bug or whatever, I have it since 23.0.7 and this example I did it in 24.0.1.

Thanks por your help.

Software Version:

FlexSim 24.0.1

proces flow subflow tasksequences

1707771662453.png (137.1 KiB)

· 2

Anutt K commented · Feb 13 at 06:41 AM

Can you attach the model file ?

2 ·

Santiago Serrano Anutt K commented · Feb 13 at 11:03 PM

prueba sub flow.fsm

0 ·

prueba-sub-flow.fsm (84.0 KiB)

Answer 1 · 2024-02-13T23:06:36Z

Jason Lightfoot answered Feb 13, '24 Jason Lightfoot commented Feb 14, '24

On the runsubflow you need to turn off Label Access on Parent Only:

For every task sequence that is created it's overwriting the parent token's taskSequence label with the next one so at some point the active token's taskSequence pointer is pointing to the wrong task sequence, and the active task sequence just waits for a new task that never gets added.

1707865592862.png (13.4 KiB)

· 2

Santiago Serrano commented · Feb 14 at 03:12 PM

That work. I only give acces to read Parent label and works well

thanks

0 ·

Jason Lightfoot ♦ Santiago Serrano commented · Feb 14 at 03:30 PM

What it does is give the ability to add/write labels on each child token, instead of forcing it to use the parent token's label.

0 ·

question