- v1.0.0-latest-prod
Resolved race condition that could cause scheduled jobs to execute an unexpected second time when the cron triggers a job execution.
More details on the observed behavior prior to the fix: Every 30 seconds, the scheduler will attempt to update all crons if the job details have been updated since the last check. However, the update timestamp is changed on every execution resulting in the scheduler updating every schedule for every job on the next check. If the scheduler attempts to update a job’s schedule in the same second after a job execution, the job may re-evaluate and run immediately for a second time.
Remove unnecessary error logging related to OFF_SCHEDULE ScheduledJob executions.