Inaccurate lactate threshold results continue in 21.19

Same problem here. Since the new version my LTH and MaxHR is completely rubbish. Before it was comprehensible. DSW is useless now.

Do you measure it with chest strap? 
I have a latest version installed and use HRM PRO+ in my runs. So far had two runs with new version installed.
It looks good for me, but let's see if it is a watch sensor related. What should I be looking at?

Yes, but I have the HRM Tri

How do you know that it is incorrect?

Because the current pace is unrealistic. It jumped from 8:33 to 7:33, which is definitely not my threshold and my 0% - 14% execution scores on my subsequent runs prove it. 

And MaxHR gets change even if auto detection is off. This needs to be fixed, how can such a flawed algorith be released?

Right? What’s the point of the beta program? This issue was known over the last couple of versions. 

Today after a considerable break, my pace improved unrealistically by 30 sec. Heart rate declined by 1bpm which is what I would expect.

I used HRM Pro+ with source switching off.

Before version 21.19, there was a guided test that you would run when you wanted to know your lactate threshold, but now there isn't. Previously, when an activity met the requirements to detect a lactate threshold, it would ask you if you wanted to save the new lactate threshold, but now it doesn't. Additionally, it doesn't seem like the criteria for detecting the lactate threshold are working properly now. Today, for example, 42 minutes of running with an HRM-Pro, more than 80% of the activity above 80% of maximum heart rate, and it did not detect the lactate threshold. Why make things worse by changing something that worked well?

Even more head scratching, these flaws were all pointed out in the betas, yet they released it anyway