My deployment uses a number of cron-jobs to regularly do housekeeping, updating data etc.

I noticed that sometimes the UI shows the Cronjob as running for multiple hours, when actually the logs show that the job finished and the container status being removed. The job has a few newer runs that show the status as completed.

I think this happens when a deployment happens during a job run, but I'm not 100% sure.

This is probably just a UI issue, and it seems not to be breaking (besides me and my inner monk). But as there's a chance that there's something running in the background that is taking up compute resources I wanted to address this here.

I found this thread, but it looks like the case being a bit different there.