Process Flow error about Exit Zone instance

Question

question

xiaocheng xie asked Apr 29, '19 Jordan Johnson commented Apr 30, '19

Process Flow error about Exit Zone instance

Hi guys, When i run a model using PF tools，some errors like the following appeared. from the message i know it is something about exit zone instance，but i don't know why. Any explainations or advises are appreciated!

exit-zone-error.fsm

Software Version:

FlexSim 18.2.3

processflow exit zone

exit-zone-error.png (30.6 KiB)

exit-zone-error.fsm (21.3 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2019-04-29T15:53:24Z

tannerp answered Apr 29, '19 Jordan Johnson commented Apr 30, '19

Hi @xiaocheng xie,

This exception can happen when there are too many events happening simultaneously. In order to alleviate the problem, you can simply add a Delay activity with time "0" in front of the Exit Zone activities. As I understand it, this gives the token one fraction of a second longer to "breathe" before another token enters and takes its place.

Hope this is helpful! Here's an updated model that runs without problems.

18824-exit-zone-error-1-1.fsm

small-delay-breathe.png (40.6 KiB)

18824-exit-zone-error-1-1.fsm (20.6 KiB)

· 3

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

xiaocheng xie commented · Apr 29, 2019 at 10:29 PM

@Tanner Poulton，

Thank you for your reply! yes,your method works, and I think it is a basic function to deal with simultaneous events.maybe in the furture development plan, you can improve this issue.

1 ·

tannerp xiaocheng xie commented · Apr 30, 2019 at 03:51 PM

Thank you for the feedback. There are a handful of instances where creating a "breathe" activity is necessary or helps avoid errors, so we might not be able to address them all, but this is one that we're aware of.

0 ·

Jordan Johnson ♦♦ xiaocheng xie commented · Apr 30, 2019 at 06:20 PM

This is actually a bug, which has been fixed, and will be released in the next bug fix release. For now, you can use Tanner's workaround.

0 ·

question