This is indeed a "bug" in the software.
We're working hard toward a solution and expect a resolution within the next week. Please check back for an update on this issue in a few days.
