This is a bug that seems to have just cropped up and we’re treating this as a high priority item. Please bear with us and we should see this being resolved shortly in an upcoming maintenance release.
Hi Eric: just wanted to let you know that we’ve made some improvements that should roll out with the next maintenance release over the course of the next week or so and that ought to resolve this issue for you.
Thanks for your patience and support while we worked through this 🙂