Some information on Scheduled Jobs in ServiceNowSummaryWhat are Scheduled Jobs? Scheduled Jobs are automated pieces of work that can be performed at a specific time or on a recurring schedule. How to Identify if a scheduled Job is Out of the Box? When the Created and Updated columns for on sys_trigger table shows its by system or admin then that particular entry is an OOB entry. The recommendation from ServiceNow is not to update these records. If the Created and Updated columns has users from the instance then these jobs were either created or updated by users and they are customised and not Out of Box. What is the system ID field used for? The system ID field is used to pin a job to a specific node. There are a number of Out Of Box jobs which run and are pinned to all nodes, Here is an example of OOB jobs which are pinned to a node: https://xxxxxx.service-now.com/sys_trigger_list.do?sysparm_query=system_id!%3DNULL&sysparm_view= ServiceNow do not recommend pinning custom jobs to a node. An example would be if ServiceNow performed a AHA transfer. The specific job (pinned) would then be forced to run on the standby node and would impact performance. The node may also be removed from the cluster but the job would still be pinned. Schedules with System ID "All Nodes" or "Active Nodes" When viewing this column you will see that most of these job have the value 'All Nodes' or 'ACTIVE NODES' which confirms that these are 'parent' jobsThese records will never actually run themselves but instead spawn child jobs (of the same name) for each application node required by their definitionFor example a job with a 'System ID' of 'All Nodes' means that there should a child job for all primary and standby application nodesThose with a 'System ID' of 'ACTIVE NODES' means that there should be a child job for only the primary application nodesThese are typically jobs that need to run the same event processor or other jobs that need increased processing bandwidth across the platformAny job with these values in 'System ID' field can be safely ignored without impact to your instance