ETL job status inconsistency between logs and database

[1t5j0y]

Run end time for an org in the db is consistently before the end time in the logs. Sample:
Logs:

2024-03-13 03:52:55,590 INFO  Avni ETL_Worker-1 [etl.service.EtlService] Running ETL for Schema: jsscpuat_new, DB User: jsscpuat_new, Schema User: jsscpuat_new
2024-03-13 03:53:50,078 INFO  Avni ETL_Worker-1 [etl.service.EtlService] Completed ETL for schema jsscpuat_new with dbUser jsscpuat_new and schemaUser jsscpuat_new

DB:

Org	Run Start	Run End
JSSCP UAT NEW	2024-03-12 09:22:55	2024-03-12 09:23:30

For the parallel runs we saw in the db yesterday, as per the logs they were still executing sequentially.
Logs:

2024-03-13 03:53:50,238 INFO  Avni ETL_Worker-1 [etl.service.EtlService] Running ETL for Schema: gdgs24uat, DB User: gdgs24uat, Schema User: gdgs24uat
2024-03-13 03:54:11,168 INFO  Avni ETL_Worker-1 [etl.service.EtlService] Completed ETL for schema gdgs24uat with dbUser gdgs24uat and schemaUser gdgs24uat
2024-03-13 03:54:11,251 INFO  Avni ETL_Worker-1 [etl.service.EtlService] Running ETL for Schema: sncu, DB User: sncu, Schema User: sncu
2024-03-13 03:54:18,242 INFO  Avni ETL_Worker-1 [etl.service.EtlService] Completed ETL for schema sncu with dbUser sncu and schemaUser sncu

DB:

Org	Run Start	Run End
SNCU	2024-03-12 09:23:07	2024-03-12 09:23:47
GDGSGOM 2024_UAT	2024-03-12 09:23:07	2024-03-12 09:23:41