There were some back-end changes in the recent release that were a prerequisite for fixing this for good. Now that these changes have been implemented, we have some additional work planned to resolve this. I can’t provide any specific timelines, but this is something that has seen some movement behind the scenes.