Teardrop issue, anyone seen this before ? (V8.0.x) Same Issue

I have a Rev A design that was done on ver 8.04.
I’m now revising this design…new file… to Rev B.

Suddenly I see this teardrop issue on one particular component pins that does not show up in Rev A design.
The funny thing is that this part has 5 pins with teardrops, but only two of the pins are showing the problem.

Very annoying as if this isn’t caught before sending out…

A temporary band aid is to select the pin and open the properties box and then just OK and close it. The teardrop then gets regenerated. But, everytime a copper zone is generated, it returns.

Yup . . . I have seen it before and fixed it, not exactly sure how but partly by working through all my issues raised when updating from the schematic.

After further inspection, the problem is due to…MISMATCHED NETS. Pin1 & Pin 3. For Rev B.

But it gets weirder. The initial problem actually starts in Rev A. That is, Although both Rev A and Rev B schematics and board routes are the same, in Rev A the connections are incorrect BUT show NO ERROR.

Now in Rev B it’s puking. My quick and dirty fix was to simply flip-flop pins 1&3 on Rev B in the layout part.

Highlighting the nets in Rev A for all tracks and pads looks correct, BUT closer inspection shows a wrong pin number connection at the part in question. How does that work?

Did I somehow inadvertently force the wrong connection in Rev A? No clue.