@jmjones – I’m wondering if you are seeing the same issue as I described here …
Last I read was that the “fix” was targeted for inclusion within FW 8.0.