This is a known issue which usually occurs when there is a discrepancy in different NSX-T latency profiles which usually happens due to one of the below or combination of below activities:
There are multiple reasons for this issue to occur, see below mentioned KBs respectively for the resolution.
Issues with NSX Latency profile state entries which needs to be cleaned up using script(s) available with support team.
If you believe you have have encountered this issue then to investigate this further