question

Elle avatar image
0 Likes"
Elle asked Elle commented

Task executer stopped working

Hello!

Could someone please help me point out what is wrong with my logic?

Please see attached:

draft solution 1.fsm

draft solution 2.fsm


At around 13000 seconds, floorstorage10 was filled up and task executer #2 stopped working. What I would like to happen is once the pallet's assigned floorstorage is completely occupied, the task executer will need to wait and then load the pallet onto its assigned floorstorage once a slot opens.


From my previous queries here, (where "if a pallet is waiting for a given time, then it will go to a queue pad") the "max timer" on the "find slot (with timer)" helped me resolving my issue at that time (https://answers.flexsim.com/questions/138951/temporarily-place-items-on-a-queue-once-floorstora.html).

So, I tried this logic by modifying it and changing the destination from a queue to "token.floorstorage" but it is not working.

1680374534841.png

I also tried simplifying the logic above where if a pallet can't find a slot for a given time, then the token will move on to "Find a slot" (hopefully by the time token moves to "find a slot" floorstorage has an available slot for the pallet to be placed"). However, the tokens are just accumulating in the "Find a slot".


1680374404329.png


I am not sure how to properly create the logic but i'm thinking maybe some sort of a decision node where it keeps looping until a slot opens?


Really appreciate your time to help!


Thanks,

Elle


FlexSim 22.2.2
task executer stopped workingwait item before loading to floorstorage
1680374404329.png (37.1 KiB)
1680374534841.png (33.9 KiB)
draft-solution-1.fsm (710.6 KiB)
draft-solution-2.fsm (718.3 KiB)
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.

1 Answer

·
Felix Möhlmann avatar image
0 Likes"
Felix Möhlmann answered Elle commented

The Max Wait Timer and subsequent release to a different activity is meant for cases where you want the token to do something else, when it couldn't pull/acquire something. If the token must wait until it has found a slot in any case, using more than a single activity doesn't make sense as it doesn't anything about the logic (the second Find Slot uses the same query as the first after all).

The actual issue is that you placed the Wait for Event activity to wait for the arrival at the decision point after the Find Slot activity. This means that it is possible for the token to be delayed long enough (until it can find a slot) so that the item has already arrived at the decision point and the token gets stuck in the Wait for Event, since the event has already fired.

If you simply wait for the arrival at the decision point before looking for a slot, the model should run correctly.

capture.png


capture.png (15.5 KiB)
· 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.

Elle avatar image Elle commented ·
Hello @Felix,


Okay, I think that makes more sense.

I've tried for all my models and it is working!


Thank you very much again :)

0 Likes 0 ·

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.