This is probably due to a forced language identifier change during project migration to Paratext 8. This has happened on two different computers in our migration workshop.
The question is, how to fix this? The link seems to have been made since the correct senses are being shown, but the lexical term itself only shows as three question marks.
