That was a bug in the system. That issue should have been resolved yesterday. Please update if the problem persists!
