Is this a bug in flow simulation?  I noticed this issue in 2015 SP4 and upgraded to 2016 SP4 and this version still has the same issue.  I really don't get it.  Any help would be appreciated!