Some records on Schedule [sys_trigger] table have next action in the past.SummaryThe key to understanding these jobs is the 'System ID" field which highlights if the job needs to run on a specific application node: 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 secondary application nodesThese are typically background maintenance jobs required for general node health and managementThose 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