question

Mischa Spelt avatar image
0 Likes"
Mischa Spelt asked Phil BoBo commented

Process flow creating task executer flow item + network nodes

A customer found an issue when creating task executer flow items into a queue connected to a network node. Please see the attached model. What makes this issue interesting is that it seems to break on some flow items, but not all of them, and after a while the error cannot be reproduced unless you restart FlexSim. So it sounds like some sort of uninitialized memory issue. It breaks in both Update 1 and the beta of Update 2.

createteflowiteminqueue.fsm

FlexSim 17.1.4
bug reportnetwork nodetask executer flowitem
· 1
5 |100000

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

Sam Stubbs avatar image Sam Stubbs ♦ commented ·

Wow, you're not kidding. Not only does the model break, but (at least in my case) it caused FlexSim itself to crash. I'll let the developers know to look at this one.

0 Likes 0 ·

1 Answer

·
Phil BoBo avatar image
0 Likes"
Phil BoBo answered Phil BoBo commented

It looks like the bug is happening because of the timing of what is happening in the Create Object activity. Once the exception has happened, the unload task isn't working correctly for any of the task executer flowitems until FlexSim is closed and restarted. We'll look into it.

In the meantime, you can work around this issue by creating the flowitems in a processor with 0 processing time instead of a queue (or upstream, feeding the queue), rather than creating them in the queue directly. This will ensure that the Create Object activity event is completely finished before trying to send the task executer flowitem in the Request Transport field. See the attached sample model. createteflowiteminqueue-workaround.fsm

You can also use the Create Object activity to create flowitems directly attached to the network by selecting a network node as the "Create In" object. This way, you can create the items and give them tasks directly from Process Flow rather than using the Task Executer as Flowitem picklist option in the queue. See the attached sample model. createteflowitem-alternativemethod.fsm


· 3
5 |100000

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

Mischa Spelt avatar image Mischa Spelt commented ·

Thanks Phil, we did figure out the workaround of creating it in an upstream queue. Glad that you found the cause.

0 Likes 0 ·
Mischa Spelt avatar image Mischa Spelt commented ·

Don't know when you fixed the bug, but it definitely works in 17.2.1.

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Mischa Spelt commented ·

Yes, this was fixed in 17.0.8 / 17.1.5 / 17.2.0.

17.0.8 release note:

  • Fixed exceptions when using the Create Object activity in conjunction with the Task Executer as Flowitem picklist option.
1 Like 1 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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