An application might want to add flows on the flows that expire after a given time – idle/hard timeout of 't'seconds.
So as an application it is desired that the flows do not exist on the switch after 't' seconds. But if
1. the switch restarts before the timers expire, the flows are re-provisioned resulting in rest of the timers.
2. the tcp connection is severed, the flows do expire, but when the switch reconnects the flows are replayed again to the switch , which is undesirable.
So in all cases where the switch reactively removes flows, the switch ends up with an undesirable flow-set post restart or reconnect.
Marking the Bug as critical as it might require a change in the way the reconciliation framework works.
Also it affects the traffic since the traffic is routed through undesirable routes affecting the application intent.