This was a bug that was fixed. If you are seeing recent instances of this, contact support.