The problem, I believe, originates in the buggy TreeSync code. The standard answer from support personnel is to unlink the trees and redownload or reupload. For users of FTM 2012, this potentially means the loss of a huge amount of work, because a lot less data synchronizes between FTM 2012 and AMT than does FTM 2014 and AMT. In other words, not a good solution for many users. It also does nothing to fix what's causing the phantoms in the first place. The developers, I assume, need information on trees where this is repeatedly happening so that they can fix it.