How to stop discovery from updating the retired CI's.

[pratiksha5]

How to stop discovery from updating the retired CI's. The operation team created a new machine with the same name. Now discovery is updating the retired CI not the new one. 

[Rahul Priyadars]

Simply retire manual CI Inclusion rule will discard this ci Let discovery update the discovered ci. Regards RP

[doug_schulze]

Make sure it was in the same class, the manually created one. That you dont have any precedence rules and maybe change the discovery source?

[Kelly Logan]

This does not seem to work when using the API to create/update CIs. The inclusion rule is ignored and the CI is updated. Any idea why? 
For details see:
createOrUpdateCIEnhanced ignoring Identification Inclusion rule 

[pratiksha5]

Create precedence rule. Define the discovery source. That will help 

[Kelly Logan]

Has this changed, @doug_schulze ? An inclusion rule to ignore retired CIs is not working for me in San Diego when handing data to the IRE via API. See my post here for details: createOrUpdateCIEnhanced ignoring Identification Inclusion rule 

I have tried != Retired, I have tried everything but Retired, I even tried requiring a Status that no CI has, and the IRE ignores them all and continues to run the match in all cases. I haven't found a switch for the API call that turns inclusion rules on/off, but maybe they aren't coded or are off by default?

Any information on this would be appreciated.