There is a conflict detected with your current scheduled time. Please contact customer support to have the conflict moved or choose a new scheduled start time. - Support and Troubleshooting

There is a conflict detected with your current scheduled time. Please contact customer support to have the conflict moved or choose a new scheduled start time. Related Links

An instance DB and nodes will be hosted in a Physical server. These Physical servers need OS patching and ServiceNow makes sure the security patches for these physical servers are up-to-date.

There will be internal patching scheduled for these physical servers and in most cases, you will not be noticing this as there are multiple nodes scattered against multiple physical servers for an instance, and patching to a physical server will not impact the instance availability.

These internal patches work on a schedule and will be created a few days in advance after careful planning.

While scheduling a clone; if you get a message as "There is a conflict detected with your current scheduled time. Please contact customer support to have the conflict moved or choose a new scheduled start time. "

This message means one of the nodes of the target is having another change during that time. This can be a patching change/ or another change for the target instance( existing restore/existing clone/any other automation)

Changes for the Source instance will NOT be causing conflicts for Clone/Restore schedule to the Target instance.

The remediation for this is as follows:-

If the original time you selected is 15:00; if you set the new time as 10:00 or 19:00; this should accept the clone schedule time as the patching is very quick and it will lock the physical node for close to 4 hours before and after.

In most cases, if you select <>4 hours from your specified time this will work. If this doesn't work with that you can try 5 hours and it should work.

If the clone is very urgent and it needs to be at that exact time you are after; please contact customer support and we can try to work with our Infra team to reschedule the patching to a different time which needs more planning.

Please keep in mind that it is always better to patch the physical server at the earliest availability to make sure it is all up-to-date for keeping the environment secure.

This can also be a reason when the Upgrade Slot is not available while scheduling/rescheduling the upgrade for an instance( this is not applicable when you are trying to schedule the upgrade for the current day). Change on Source instance WILL be the reason while trying to select a window for your Upgrade schedule and the slot is not available.