Timequest: Tri-state node assumed to be a clock

Strange. I've had a similar situation where I don't know why it thinks it's a clock and in TimeQuest, will manually run:

create_clock -period 10.0 -name not_a_clock {fmrc:fmrc_i|bus_tri_d}

report_timing -setup -detail full_path -npaths 20 -to_clock "not_a_clock" -panel_name "to not_a_clock"

report_timing -setup -detail full_path -npaths 20 -from_clock "not_a_clock" -panel_name "from not_a_clock"

If any paths show up, then look at what's being clocked by that. (From the screenshot you sent, I can't imagine what this would catch. I'm just saying this has worked for me. In my case it was a node with a large fanout and lots of logic, and somewhere in the many pieces of code it was actually used as a clock, so this just helped me find it quickly)