question

Patrick Cloutier avatar image
2 Likes"
Patrick Cloutier asked Patrick Cloutier commented

How to restart Token Creation after a bug in model?

This happens to me quite a lot in different models while building and debugging a Process Flow: After a bug such as below, the Token Creation stops working even if I press Reset and Run. The only way to restart the Token Creation is to close and reload the model. Is there another way to restart the Token Creation?

It happens in any FlexSim version.

time: 0.000000 exception: Exception caught in Executive::tick(). Throwing.

time: 0.000000 exception: int runthemessageloop() #4

exception: Executive::instance.tick();

FlexSim 20.1.0
flexsim 20.1.0
· 2
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Patrick Cloutier avatar image Patrick Cloutier commented ·

I noticed that the inability to restart token creation happens only if that type of error occurs at time 0. If it happens anytime after that, there is no problem because reset effectively resets everything as it should.

0 Likes 0 ·
Patrick Cloutier avatar image Patrick Cloutier Patrick Cloutier commented ·

So I just added a 1 second delay at the beginning of my process flow. So now the errors do not occur at time 0 so I can always reset and run.

Its a patch.

0 Likes 0 ·

1 Answer

Jordan Johnson avatar image
1 Like"
Jordan Johnson answered Patrick Cloutier commented

There is a bug with the Scheduled Source where this can happen. If that is the bug you are seeing, then the only solution I'm aware of right now is to re-create the source. You can copy/paste the Scheduled Source, and the new one will work.

I'll link this case to that issue on the dev list.

· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Patrick Cloutier avatar image Patrick Cloutier commented ·

Or, as I did above, add a 1 second delay at the beginning of the process flow (after the Source) so that when a error occurs it is no longer time 0.

Thanks,

0 Likes 0 ·