I think this was a bug in the site, which appears to now been fixed.