Clone automation restarts nodes while scheduler set to 'specified' - Known Error

Clone automation restarts nodes while scheduler set to 'specified' Description Post clone, application nodes may not have the correct scheduled job configuration.

Specifically jobs with parent record set to 'Active Nodes' fail to be created per application node preventing them from running

This will impact several areas of the platform including event processing

Steps to Reproduce

Review a recently cloned instance for which application nodes have not restarted post clone

Workaround If an instance has been impacted then no jobs set to 'Active Nodes' will run. You have two options to fix this issue:

Restart the instance - This can be requested from ServiceNow by raising a new Case via the NowSupport Portal Manually trigger the creation of the jobs. This is a straight forward process that can be actioned as follows: Navigate to sys_trigger.list Filter for all jobs where 'System ID' = 'Active Nodes' For each record perform the following: Open the record Update the 'Next Action' time and increase by 1 second Save the record This will generate all the child records for these jobs and restart processing of events and other functions