question

There are a few problems with your model.

• You need to activate a named agent behavior in order for a given agent to do proximity checking using that behavior. Merely calling Agent.System.createAgent() will only add the agent to the system, making it detectable to other agents who have activated behaviors. Since you don't have any agents with an activated behavior, none of the behavior's triggers will fire. I added the following code to your trigger after creating the agent.

agent.activateBehavior("Proximity Behavior");

• The OnEnterProximity and OnExitProximity logic don't really make sense in this model, because you don't have a behavior named "Narrow Phase". The only behavior you have defined is "Proximity Behavior" (See the combo box drop-down at the top of the Behaviors tab).
• You need a filter to make sure that AGVs will only detect proximity with people, not with other AGVs. I'd suggest letting the standard path accumulation logic for the AGV network manage inter-AGV proximity. In the attached model I set an "AgentType" label on the people to 1, and then I added an Active Rule to the Proximity Behavior that the neighbor's AgentType label must be 1.
• The enter and exit proximity should likely instead do some logic like stopping the AGV, instead of activating a narrow phase behavior. Although you probably still want it to only stop if the person is "in front" of the AGV, not if the AGV has already moved past the person. I implemented logic in the attached model to do this, although it's not perfect. I had to move the logic from OnEnterProximity to OnInProximity because a person might move into an AGV's "field of view" after entering proximity, but even then it isn't quite right.

Even when you do these things though, I don't think the result is perfect for what you want. It seems the "viewAngle" i.e. the amount that the person is "in front of" the AGV, which decides whether to stop the AGV or not, is a hard value to get right, and I still get some instances where they overlap.

Instead, I would suggest a different approach that uses a control point as the "agent" that is detecting proximity with people. I added this second option to the model. The control point keeps track of how many people are in its zone. Then a process flow will detect its AGV pre-arrival event, and if the control point has people in its zone when an AGV arrives, it will stop the AGV and wait until the people in its zone get back to zero. The relevant elements for this part of the model are the the CPxPersonProximity process flow, the ControlPoint5 Process Flow, and the ProximitySystem2 agent system.

agentproximity.fsm