Ticket #5521 complains about prediction pred-000483. The lookup
below "finds" a record every time — but it matches on the output
text, so it returns the first prediction that ever said
will_churn, which belongs to a different customer and a different
model version. You'd ship an explanation for the wrong prediction
and never know.
Fix the condition on line 14 so the join uses the complaint's prediction ID.
Expected output:
pred-000483 | churn-clf-v13 | 388ms
The break is on line 14 — but read the whole snippet first.