question

The loading arm and berth have some internal communication going on that gets disrupted when you just disconnect the loading arm and kick out the vessel. The main reason your berth stops working is the loading arm stays assigned to the barge and will not release the position on the berth until it detects the target level.

As a workaround, you could try not disconnecting the vessel manually, but scheduling the message it expects, using the following code in Disconnect Loading Arm.

FlowObject loadingArm = token.bargeCompartment.as(Object).outObjects[1];
destroyeventsofobject(loadingArm);
createevent( loadingArm, 0, 0x81300, "", token.barge );
//token.bargeCompartment.as(FlowObject).output.ports[1].disconnect()  ;

The constant 0x81300 is the internal code for the "Loading complete" event. See the attached model 24067-sample-model-partialrecycle-ms.fsm.

I hope that provides a solution to the problem. As said, this is more of a workaround. The Berth/Loading Arm is suitable in most simple cases, but if you seriously start simulating port operations our experience is it is often better to replace the berth with a Queue or Basic FR and the loading arm with a Pump, then do the connecting and waiting logic in Process Flow. We have done this a few times ourselves, and were planning to add a Process Flow template to the FloWorks 20.0 release similar to the attached example berth-with-processflow.fsm.