Actually - I just had a thought. I wonder if some other content installed a 'shoulder fix', which might be confusing the DSON task search algorithm? In my early days of DAZ and G2F I installed everything I found ... assuming like V4/A4 in Poser, that a new 'pose' had no impact unless applied.

Yet DSON builds a CR2/PMD (it seems) with EVERYTHING in the /data directory, so in effect every fix/change gets padded into the scene, even if the dial is 0.0 always. Given the vague names in the DUF, this could lead to name-space issues (something I am familiar with in Python, where HOW you import a modules means the same code be in RAM multiple times as different namespaces).