Scheduled Job getting triggered twice after cloning due to 2 sys_trigger jobs assigned to the same scheduled jobIssue After cloning, Scheduled Job getting triggered twice due to 2 sys_trigger jobs assigned to the same scheduled job. ReleaseOrlando Patch 7Cause-- Hop onto the instance. -- Navigate to the sys_trigger.LIST -- Search with the affected scheduled job name under triggers list -- You will notice 2 sys_trigger jobs are sharing the same sys_id of the scheduled jobResolution-- Before applying the workaround, We request you to take backup XML of the record. -- We suggest you to delete one record in the sys_trigger table and it will resolve your issue.