I have been told by Microsoft will be fixed in CU2.

I have the same problem and as we monitor msdb.dbo.log_shipping_monitor_secondary I wrote the following work around to the SQL 2019...