Hi blackcat,
I'm sorry to hear of your frustration. I will continue working with you on this issue through your open support case until we can reach a resolution but I'm inclined to update this thread in case anyone else comes across it that needs assistance with a similar situation.
We were experiencing a technical problem that was causing some users to experience this behavior Tuesday morning in the wake of our release, but we pushed out a code change later that day to resolve the problem. I am no longer able to reproduce the problem in your account so I suspect your browser still has some data cached from before we released the fix.
If anyone else is encountering this problem, you will most likely be able to resolve the issue by clearing your browser cache and then closing and reopening your browser. If you continue to experience the problem after that, please file a support request from our help page and we’ll be happy to continue assisting you.
-Mike
