It's likely this was just a temporary glitch that will clear itself up when you click the Back button and try again. We've been notified of the issue and will investigate further if it doesn't resolve itself.
