Try setting the status to None first, that might clear the issue. You might have to wait afterwards about a minute.
The short explanation of the problem (assuming it's the same one) is that a bug from a while ago that has since been fixed essentially corrupted certain reading status entries...