Reapply Lookup Rules UI action not reapplying all VITs

dan167
Tera Guru

Hi,

 

We recently updated our VR plugin to 26.5.3 and I have noticed that the reapply lookup rules UI action on the discovered items table is not updating all of the VITs that it used to.

We have a process for unmatched/unclassed CI's where someone goes in and deletes those from the CMDB tables and then we reapply the lookup rules so that the VITs associated with the deleted CI's get updated to the correct CI. After updating the plugin it does not appear that the reapply rule is updating the VITs.

 

I noticed in the release notes of the previous versions there was an update to the lookup rules

"Lookup rules enhancements: When you reapply Lookup rules, discovered items (DIs) that have been inactive for more than 90 days are ignored. These DIs are also excluded from licensing considerations. Removing them from the lookup logic can improve performance and reduce processing time." Version 26.0.11

 

The discovered items in question are not over 90 days inactive so I am not really sure what the issue is here. When I go to reapply the look up rules i have added filter for state = Unmatched or Configuration item is empty. I reapply the rule on the filtered items but the VITs do not get updated that have an empty CI.

 

Anyone able to give me some clues on what to look for here?

2 REPLIES 2

Eliz Skogquist
ServiceNow Employee

The job is configured to run weekly with a 1000 record limit for performance reasons.  If you look at the 'Re-apply CI Lookup rules on the Changed Discovered Items' job, you will see the 1000 limit.  Update the frequency of the job triggering to complete execution across the entire table. You can increase that limit, but suggest small increments as it can impact performance.  Try to keep that number below 15000, and increasing to that size should be completed with caution.  KB1695110 covers this information https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1695110 (you will need a log in to Support to have access to this KB)

Thanks will take a look at that job