question

I don’t think it is a bug. It is more a misunderstanding of process flow. Most options in 3D object properties are designed to be part of a fixed resource logic, but process flow is a logic structure beside the standard 3D logic. If you start to implement process flow, as it is recommended, to control a model, you leave the path of 3d standard logic. You are responsible to read option parameters in process flow by your own and then delay tokens.

If I build a process flow structure, I try to build a 3d standard logic model first and then incorporate process flow as a substitute of written triggered source code.

There might be a slightly difference in the task types load/unload vs frload/frunload, too. load/unload matches better with a process flow logic, but both tasks aren’t anymore involved with the concept “number of items in transit” of standard 3d logic in process flow activities.

There are templates of process flow which emulates a 3d logic perfectly, but it is still an emulation and not a native 3d model logic. Please don’t misunderstand me, I am a fan of process flow, but not as it is introduced in tutorials. For me it is a supporting tool to document a written source code in a better way and not as a replacement. A classic 3d logic of connection edges “create>store>process>destroy” driven by FlexSim engine has still not found a suitable replacement in process flow with all dependencies you have implemented back from your earliest FlexSim versions like 2.6 or 3.5.