Hi Paul,

Thank you for your prompt response. I'll pass this on to her and get back with the results tomorrow since she has today off. 

However, personally, it is disappointing that your proposed workaround (not a solution) involves sacrificing a key function that I been championing within my team as a solution their complaints about the slow "TM searching" that happens every time they move to the next segment. I value Lookahead even though it's buggy and causes the results window to jump to the previous segment (for me at least, but I ignore this problem). It's unfortunate that a key 2017 function that delivers speed and efficiency will have to be sacrificed for the sake of regaining essential TM functionality. I hope I won't be accused of being out of line for saying that.

This same topic was discussed here:

https://www.proz.com/forum/sdl_trados_support/271117-studio_2014_duplicates_when_updating_tm.html

https://www.proz.com/forum/sdl_trados_support/172292-sdl_trados_2009_tm_segments_not_updated_but_added.html

And several posters shared my (and most disappointingly, my team member's) frustration in a lack of consistency. It didn't seem like any solution was found in either tread. And just to clarify, the duplicates do not occur after an "update main translation" memory batch task where the "always add new translation" option is available. But just in case, is the "Always add new translation to the translation memory" option also applicable to in-editor corrections? I assume since that option only exists in the "update main/project translation memory" batch tasks that that option would only be applicable there for batch tasks and not in-editor updates. http://producthelp.sdl.com/SDL%20Trados%20Studio/client_en/Edit_View/TMs/EVTranslationMemoryActionsUpdate_the_TMwith_New_Translations.htm
Kindly correct me if I'm wrong. 

Keenan Cooper said:

I thought such penalties would only apply to duplicates from different TMs.

Hi Keenan,

I just wanted to chime in and say this also happens when you manually add multiple translations to a TM, but that's, of course, intentional.

However, if I'm understanding correctly, your colleague is not using the Add new translation option, but rather is confirming her segments as usual.

I was trying to see if I could repro this, as I hadn't necessarily noticed it happening, and I can report that I've been able to reproduce it.

Here's a video showing the issue as I'm seeing it. It doesn't happen all the time, and it doesn't necessarily happen on the same segments, that is, if you go back to the same segment and change its translation multiple times, sometimes the TU will be overwritten and sometimes it won't. LookAhead is disabled, but that doesn't seem to make a difference. I also tried with my main TM and with a new, empty one, and the issue happened with both.

Paul Filkin are you able to reproduce this as well?

Okay. I did Skype screen sharing with my coworker and worked through the setting changes (not incredibly computer literate). To both of our shock, this worked. Thank you, Paul. Turning off Lookahead, then repeating changes and confirmations to the same segment showed just a CM or 100% hit in the results window. No duplicates. As it should be. We turned Lookahead back on and it worked normal, with no duplicates, much to her surprise as well (can't stress this enough). It generally worked fine except a couple times after changing one segment, the same segment would show the previously confirmed edit, not the new one, but not as a duplicate. Just 100% match of an old hit despite confirm a new version of it. This was with Lookahead on, and I know that sometimes there's a lag with the search results so refreshing the view would fix it. I forgot how to refresh the results window (Ctrl something?) but changing the TM project settings a couple of times and it refreshed and worked again. Hopefully, in the future, this lag can be fixed confirming a segment will refresh the results automatically.

Side note: When not translating myself, I spend a decent chunk of my time troubleshooting for my coworkers... to the point where I take regular support tours to their workplaces to help, fix, teach, and refresh their memories hands-on. Despite my role as the ad hoc expert within the company, I would never have guessed that "resetting" lookahead would fix it. I often encounter problems that baffle me so I just end up apologizing on behalf of the software (it was my idea to use trados in the company so I feel responsible). So yeah, forgive the constructive feedback, but some solutions are not instinctive to me and even less obvious to my less computer-literate, Japanese speaking co-workers.