You definitely want to verify the Netflow is configured correctly to send both in and out traffic for the interface, which can be verified via a pcap as stated above. That is usually the cause of this behavior.
In some cases, where the netflow data is correct, we have seen that rebooting the Harvester can resolve this, although this is rare as its usually due to router configuration.