Trace Analysis Results for Action Node 5 enqueued packet to node 4(node5_+_node4)

This text provides more details for action Node 5 enqueued packet to node 4(node5_+_node4).
Action is of type: local, supposed to change variables of a single process only.
Action Node 5 enqueued packet to node 4(node5_+_node4) occurs 3 times, which accounts for 0.30 % of all events.
On average an action occurs 10.20 times, so this action is below average.
Action occurs at position 59 for the first time, at position 249 for the last time.
Note that the action is not(!) present in the last 751 events, which is 75.10% of all events. May be it becomes rare or even dead?
It never follows another action in zero time, there is always a non-zero delay observed before this action occurs.

Enabling Set and State Transformations

The following table shows for what value setting of variables the action occurs and what state transformation it performs.The table shows only those variables that belong to processes that the action corresponds to.

Variable	Enabling Range	State Transformation	Remarks
State of node 5(node5_state)	= 1	not modified	Action occurs at full range of values!
Number of packets dropped by node 5(node5_dropped)	= 0	not modified	Action occurs at full range of values!
Number of packets received by node 5(node5_received)	in {1,...,9}	not modified
Number of packets sent by node 5(node5_sent)	in {0,...,4}	not modified

List of Warnings

Type 16: Action Node 5 enqueued packet to node 4(node5_+_node4) may deadlock, because it occurs the last time at event 249 and is not seen for the remaining 75.10 percent of the trace.