question

First off:

Separators that use the 'Default Separator Option' in the 'Send to Port' field required two output connections, the first for the container item (pallet), the second for the flow items previously loaded on it.

Assigning the types and thus distributing the pallets randomly is at odds with the requirement to load in a fixed order. If one separator doesn't get a new pallet because the one on the combiner is waiting for a different separator to become free, the model will be stuck.

To demonstrate how this can be done I changed the 'Send to Port' logic of the combiner to 'Round Robin if Available'.

To have the task executer work in a fixed pattern I would suggest to use a process flow in conjunction with a list.

Instead of referencing a task executer to do the transport task directly, the separators push the items to a global list, partitioned by their type (A,B,C,D). The default option for this was slightly modified in the attached model to send the container item to the sink directly without the need for a transport. (added code marked red)

The process flow is quite simple. A reference to the task executer is added to the created token as a label. The token then first pulls items from partition "A" and then has the task executer load them. This is then repeated for types B, C, and D, with the token pulling 6 items in the latter two cases.

Finally all items are unloaded to their destination (this label is added to the item in the default part of the code above), before the token loops back to the beginning.

test-2022-1-fm.fsm