An occurence at
suggests that iSpot isn’t correctly making sure (there’s a technical term escaping my recollection here) that either all or none of the database changes relating to a user action get implemented.
As noted in the post, iSpot crashed trying to remove my agreement (500 error). That may have caused the glitch. Not sure of relative reputation points, but it may be the phantom agreement that is “holding” the “Likely” tag with the first ID.