This counter records the number of frames dequeued across the eight egress queues of this flow point during the archived historical interval. An admin uses this historical count to confirm how much traffic the flow point actually released toward its egress direction during a past period, useful for comparing against ingress byte counts to spot where loss or shaping occurred. For example, if a customer's total ingress bytes for a day were much higher than what cmFlowPointHistoryFD's frame count would suggest was forwarded, the admin would investigate that flow point's egress queues for excessive shaping or drops that day.