Just to the right of the Track number in Track View, there is a little wav icon for an audio track or a little keyboard icon for a midi track.  Why is that icon red on Track One which is an audio track?  There is no overload/clipping on that track I can find.  The meter gets to -2 peak in console view, but not higher.  Double clicking the header icon does not remove the red.

Are you talking about the WAI indicator? 

The little teeny wav icon located immediately to the right of the track number. 
https://drive.google.com/file/d/0B5NGFo_mTbPOYlZQSGFpZ1lzc2M/view
 

Ok I have not seen that as red before or I never noticed it being red before.  I wish your pic was a little higher res though. 

I can't even see this, on either your picture or when I look on my screen - I have a lot of eyesight trouble seeing little things, even up close.
 
Can you please provide a larger crop of that particular area of the screen?
 
Bob Bone
 

here ya go
https://drive.google.com/file/d/0B5NGFo_mTbPOM1FCSTNrOHJxWWs/view
 

Somebody must have changed the icon while you were away from the daw. Drag the bottom of the track strip down to reveal the larger icon, right-click on it and select Reset Track Icon.

Nope.  That just "resets" the microphone icon to the default audio wave icon.  The little red guy persists.

Oh....ok, obviously I wasn't aware of something...

So, how about enabling Views (above Control Bar) > Icons > Track View > Show Custom In Header and then resetting the icon? Does it work?

That is the "thing" about computers.  If you click enough stuff something will happen, maybe good, maybe bad.
 
I clicked Show Custom in Header and the red wave was replaced by the microphone.  When I reset it the red thing came back, then I just started my usual random clicking temper tantrum, and poof, it went away.  I searched through all the icons, and none of them appear to be that red wave thing.   In any case, it is gone.  Thanks.
 
I was worried that it actually meant something, that something in the effects chain or somewhere else was overloading.  That did not appear to be the case.