Exception Rules no longer provide option to execute on existing data

[ErikM]

I'm running ServiceNow Vulnerability Response 26.0.11. There were recent changes to VR and now exception rules no longer create remediation task to track VITs that are deferred; but I also noticed I no longer have the option when creating the exception rule to include existing data.

I have a new rule that was approved but when I look at the fields "Execute on existing data" and "Executed on existing data"; the value is false, and the values cannot be updated via the GUI.

What can I do to ensure exception rules trigger on existing data?

[Martin Dewit]

I noticed this same issue. I think the quickest/easiest solution would be to add the  "Execute on existing data" field back to the form layout.

[ErikM]

My ServiceNow admin reviewed the issue and found the "Execute on existing data" option was no longer enabled after the upgrade and were able to turn it back on. It's now visible when I go and create an exception rule.

[Manuela Jaroszz]

I am experiencing the same problem and have added the field in the form, but no remediation task is created, and the VIs that are in scope for the exception rule do not change their status to deferred. What do I miss here?

[Vratislav]

The process changed. No VG is created anymore. Besides that this is not triggered anymore by Business Rule, but is depending on scheduled job Associate existing VIs with Auto Exception Rule

Execute on existing data is not used anymore if my investigation was correct. It will always run on existing and newly incoming data. We are also facing issue with the job, some investigation is still required, because not all the VITs are being deferred, and sometimes the execution is not really working. Script itself seems ok, but maybe is blocked by some import .... ...