For now - what we have done is perform alignment in the 2017 SR1 14.1.10017.54688 and created a TM, and then use the created TM in 2017 SR1 14.1.10018.54792 as needed.

 Zara Zainol 

That is probably your best workaround now unless you are prepared to upgrade.  2017 is too old for any more fixes.

You probably already do it, but I always found the best solution with alignment is to whip through the document and manually join the segments every now and again, especially if you notice any odd behaviours.  Then realign.  That can force a mostly correct alignment and the editing is then much easier.

 Zara Zainol 

That is probably your best workaround now unless you are prepared to upgrade.  2017 is too old for any more fixes.

You probably already do it, but I always found the best solution with alignment is to whip through the document and manually join the segments every now and again, especially if you notice any odd behaviours.  Then realign.  That can force a mostly correct alignment and the editing is then much easier.

Thank you so much Paul for your inputs! Yes that's best solution/workaround for now.

I wanted to ask - have you any idea why does Alignment and the standard project analysis seem to work differently?

What I mean to say is that when creating the alignment, the source segments are relatively clean (very few tags). And then when I create a new project analysis and use the same source which was used to perform the alignment, Trados inserts several extra tags in the source segments.

This unexpected behaviour makes the leverages a lot less as I was surprised - its almost as if Trados project analysis and alignment follow different segmentation rules?