Scheduled job 'Impact VM - ITSM - Historical Data Collection' not visible - Support and Troubleshooting

Scheduled job 'Impact VM - ITSM - Historical Data Collection' not visible Issue Problem The job 'Impact VM - ITSM - Historical Data Collection' is listed as installed. However, when checking the sys_trigger table, a 'Record Not Found' message appears.

Steps to Reproduce

1. Connect to the instance with an account with admin role 2. Navigating to 'Performance/Platform Analytics > Data Collector > Jobs' 3. Query by *Historical Data Collection 4. Expected to see two jobs but only see one job.

Release Generic

Cause Root Cause The issue is caused by an invalid domain reference ('ce43143b1b28c5105021cb34604bcb5b') associated with one of the scheduled jobs, which does not exist in the domain table. This discrepancy prevents the user account from viewing the job when restricted to the domain. The valid domain for the jobs is global, and switching the user's domain to global resolves the visibility issue.

Resolution Steps to Resolve

1. The sys_property glide.sys.domain.use_record_domain_for_processes = true

When this property is enabled, system will use the record's domain for choosing which processes to run on any form When this is disabled, system will use the session domain

For example, the user is in "TOP" domain and the domain selected in Domain Picker is "TOP". And then, the user opened a Incident record from "TOP/ACME" domain.

Now, when the property is true: then on the form, the processes from TOP/ACME domain will trigger and, when the property is false: then on the form, the processes from TOP domain will trigger

2. User is on domain: _DOMAIN_1_

3. Processes are on global and ce43143b1b28c5105021cb34604bcb5b domain That sys_id "ce43143b1b28c5105021cb34604bcb5b" for domain does not exist on the domain table.

4. Update the record with domain ce43143b1b28c5105021cb34604bcb5b to domain global