Delay Activity issue. Token don't move to next activity.

Question

question

Manuel Sinco asked Jun 19, '20 tannerp commented Jun 19, '20

Delay Activity issue. Token don't move to next activity.

Hello,

I made a simple model which worked properly the first time that I run it but after that, it didn't.

Basically, the issue is that the token in a delay activity does not advance to the next activity even if the delay time has been completed. I checked the connections and they were okay. I tried to delete the delay and change it for a new one but any of this worked.

If I run it automatically, since the first time it arrives at the delay it'll remain fixed to it, but if I run it using the step button, The simulation arrives at time 19 working properly but after that again is fixed to the delay activity.

I'm attaching you the model, to see the error.Error_in_delay.fsm

Thanks,

Manuel.

Software Version:

FlexSim 19.1.2

processflow flexsim 19.1.2

error-in-delay.fsm (37.2 KiB)

Answer 1 · 2020-06-19T17:57:15Z

tannerp answered Jun 19, '20 tannerp commented Jun 19, '20

I think it has to do with the timing of everything. I added some delay activities and it seems to run just fine. There's a lot happening in 0 time the way you had it set up, and I think the Decide and Release Token activities were having issues because they were referencing a child token that had already entered the sink.

error-in-delay_1.fsm

error-in-delay-1.fsm (37.5 KiB)

· 2

Manuel Sinco commented · Jun 19, 2020 at 07:18 PM

I think that you are right. I took out some delays that you added but included a breath delay between the custom code and sink activities. Instead of releasing the token directly into the sink, I release it into the breath and works as it supposed to.
Thank you!

P.S. I don't know how to accept you answer as the correct one, based on that it's just a comment.

0 ·

tannerp Manuel Sinco commented · Jun 19, 2020 at 07:41 PM

Glad you got it to work with the proper breathe activity. I'll take care of converting the comment. Thank you for the prompt feedback!

1 ·

question