Yeah, we're just starting our 1703>1803 pilot and I'm seeing this happen too frequently in our environment.
I'll probably open a support case as the patch definition logic doesn't work 100%. If the repair task actually reported failed I wouldn't have a problem with it... but unfortunately, patch and compliance actually reports the patch applied successfully.