Thanks for flagging this. It is the same underlying cause. We re-wrote the error message to hopefully eliminate some confusion, as the previous error message was less clear than this one. As a result of our database migration late last year, we are processing submissions more quickly, which we believe is the likely cause of this error and others you are reporting.