The problem is most likely this:
a trigger that says when motion path X is completed change state of X to Visited
especially if your glitch is intermittent.
All the built-in states (like Visited) have their own specific built-in superpowers that automatically work. If you create triggers that repeat their action, you can have conflicts that are unpredictable. "Change state when motion path completes" might not be an exact duplicate of "Change state when object is clicked (the built-in version), but it might be close enough to cause your problem.
I would start by changing the name of that state (to something like HasBeenVisited) everywhere it appears in the project.