Currently start and end times are not recorded in the job_run_details table for job runs that fail to start due to connection problems, lack of available background workers when background execution is enabled, or other early-stage failures occurring before the cron task is in progress.
This change ensures that start_time & end_time are recorded for those failures. The intent is to guarantee that timestamps are always available in the log table once a job reaches a definitive state (succeeded / failed)
marcoslot
commented
6 months ago
Currently start and end times are not recorded in the
job_run_detailstable for job runs that fail to start due to connection problems, lack of available background workers when background execution is enabled, or other early-stage failures occurring before the cron task is in progress.This change ensures that
start_time&end_timeare recorded for those failures. The intent is to guarantee that timestamps are always available in the log table once a job reaches a definitive state (succeeded/failed)Fixes #246