Scheduled job not running with definition presentIssue When this happens you will typically see a scheduled job (report, script run, etc.) that is set up correctly; however, the job is not running. CauseThe scheduled job definition is not what the system uses to determine if there is a job that needs running and when to run it. When a Scheduled Job is created or updated, a record is inserted into the sys_trigger table - found under System Scheduler -> Today's Scheduled Jobs. That record in the sys_trigger table contains the last time the job was run, the next time it will be run, and what it is that needs to be run. Therefore, if you have a Scheduled Job that does not have an associated record in sys_trigger, that job will not run. ResolutionSet the Scheduled Job's active flag to false, save the record, then set it back to true and save the record again. This will force an insert of that job into the sys_trigger table.