Originally Posted by
Tracer_SEA
What I recall is that after a status change, if you have the agent remove the FF# from existing records and then re-add it, the system will then properly recognize the new status in those records
Not saying it SHOULD work that way, but that's a work-around for the issue you describe
AH! Got very excited when I saw this. Had an agent try it, but alas, no dice.
I wonder if that may actually be a sign that convergence in the data is slowly arriving. Just learned from this call that they're planning a pretty significant new rollout that's supposed to deal with some of these issues in 1Q2019. Fingers crossed...