In Microsoft SQL Server 2019 and 2017, the ForceLastGoodPlan feature for Automatic Tuning doesn't take CPU consumption of aborted queries into account in the execution plan regression detection logic. The feature recognizes query execution time-outs as client-side aborted queries. Therefore, it doesn't interfere. If the query that has a regressed plan is consistently timing out, the ForceLastGoodPlan feature won't detect and correct the plan regression.
Cumulative update information
This problem is fixed in the following cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.