Error: label does not exist, Issue with pushing item in list

Question

question

Peter asked Aug 30, '23 Peter edited Sep 25, '23

Error: label does not exist, Issue with pushing item in list

Hello,

I have a model where I use a list to keep track of my storage in the system (buffer in the middle of the model). However, I get an error at 42.73 seconds. The problem is when Waste wagons are pushed in the list (left in process flow) something goes wrong since when pulling this out of the list, no label can be assigned.

This is a screenshot of the list right before the last row is pulled. Right now I do not understand what the 'value' column means.

Could it be that I use the list wrong? I basically just want the flow item (box) to have assigned labels which is both saved in the list so it is always tracked what is in storage and can be pulled out accordingly.

Software Version:

FlexSim 23.2.0

list label

1693395351437.png (17.1 KiB)

trolleybuffer10-autosave-reduced.fsm (971.7 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 · 2023-08-30T12:34:20Z

Felix Möhlmann answered Aug 30, '23 Felix Möhlmann commented Aug 30, '23

The value is what was pushed to the list. In your screenshot you can see that the last entry is a token. It gets pushed to the list at the end of the "Waste Wagons" section. When it is pulled it enters the sink. Since it does not exist anymore, the pulling token trying to read the labels leads the error you are seeing. (Trying to read a label on a node that does not exist)

· 2

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.

Peter commented · Aug 30, 2023 at 01:53 PM

That makes sense. Thank you for your response!

So, the 'Vognbuffer/Box1~55' for instance refers to the item while the 'id: 125 instance: Processflow' refers to a token?

I guess I would need to push in the flow item not the token? How is that done?

Also, does it even make sense to track the labels on the token or would it be better (/possible) to track them on the flow item throughout the whole flow?

0 ·

Felix Möhlmann Peter commented · Aug 30, 2023 at 03:48 PM

The Push Value field determines what is pushed to the list. In your case you would use "token.pulled" (the previously pulled item).

Copying the labels to the token is not necessary but can make the many field values more readable ("token.Type" vs. "token.pulled.Type").

It can also speed up building the Process Flow, since once you define a token label somewhere, it will be added to the list of autocomplete options that pop up when you start to type a label name.

And if you access the label a lot, one less step to reach the label value will make your model ever so slightly faster.

Mostly it's personal preference I would say.

0 ·

1693410328256.png (11.2 KiB)

question