when do you get this error ?
when you add the EOs as parts, it's os agnostic. when the EO actually executes it will look at the target server's os and choose the right EO. i believe you can ignore this by checking the 'ignore asset collection errors' on the 1st or 2nd panel of the compliance job. or split this into separate templates.
I get this error when testing the rule. I usually do this before running the job to make sure that there are no fundamental errors in the logic or evaluation. Also i forgot to add that it is a Local EO, but if the tested targets are all windows it succeeds just find but if i add Linux then i get the mentioned error during the testing.
Remove the EO or split the template for each os.