I have the exact same issue, which happened for the same reason. What is frustrating is that no one on "support" or in the "community" seemed to be in the loop, despite the bug being reported for more than two years.
