We believe that there may be a caching issue. We’re working on it.
While we do, you should be able to get around it by doing this: