Exception on pull from list

[amerloQ2XZU]

[ FlexSim 21.1.1 ]

Hi,

in a model, which I can't share, an exception in system console occurs.

time: 2729.845116 Exception caught in evaluation of /Tools/GlobalLists/FRS_OUT_WaitForElevator/1/onPull

Does anyone help me to understand the error? @ or @

I never caught the exception in the past and I believe that it is related to wrong pointer or memory issue because it isn't reproducible systematically.

I can share a picture which shows an ugly data inside a global list. I never saw this data structure inside a list and I didn't create it, trust me.

Any suggestion or idea is really appreciated.

Thanks in advance!

[Jeanette_Fullmer]

Hi @Alessio Merlo,

Were you able to solve your problem? If so, please add and accept an answer to let others know the solution.

If you still need help, posting your model would be helpful.

If we don't hear back in the next 3 business days, we'll assume you were able to solve your problem and we'll close this case in our tracker. You can always comment back at any time to reopen your question, or you can contact your local FlexSim distributor for phone or email help.

[amerloQ2XZU]

Hi @Jeanette,

I didn't solve the problem because it randomly happens.

If you aren't able to provide any information to solve the issue you can close this case.

[Jeanette_Fullmer]

Hi @Alessio Merlo,

Since it seems to happen randomly it would be helpful to see your model.

Proprietary models can be posted as a private question visible only to FlexSim U.S. support staff. You can also contact your local FlexSim distributor for phone or email help.

Would you be able to share your model?

[jason_lightfoot_adsk · Accepted solution]

If your model is repeatable then delete that structure of contained nodes (also check that the object attribute structure looks as it should compared to a new list) - and then run the model with the tree view open to determine the event at which this node gets added. It looks like it's a copy of the defaultdatasource variable so it woud be interesting to know if that has been copied or moved there. If you have code that is evaluating the location of a node using 'up' it's worth noting that a simple mistake of using = instead of == will change the objects location. Perhaps something like that is happening.

[eric_m3]

Hi @Alessio Merlo, was jason.lightfoot's answer helpful? If so, please click the red "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.