Inactive jobs run after a full cloneIssue Scheduled jobs run on the target instance post clone even though they are inactive in the target instance.CauseThe issue can happen because sys_trigger is in the clone_data_preserver but not in the exclude list. Some of the records from sys_trigger are getting copied over to dev instance and run on the target when the clone is performed. If you set a data preserver on a table where the source instance has more records than the target instance, the data preserved on the target instance also includes the additional records from the source instance. For example, assume that the data preserver is already in place. In the source instance, the sys_temp table contains 100 records.In the target instance, the sys_temp table contains 20 records. After the clone, the sys_temp table in the target instance contains 100 records. The 20 records in the target sys_temp table are preserved successfully (per the data preserver specification).The source sys_temp table brings over the remaining 80 records to the target sys_temp table. ResolutionTo resolve this issue and to preserve only the records in the target table, You can exclude a table to create an empty but usable table on the target instance. for the target table, in addition to setting the data preserver on the source table. Related LinksCreate a data preserver