Jobs exit while in starting state, nothing logged

This is an intermittent problem seen especially in provisioning jobs. The job stays in the starting state, nothing happens or is logged, yet a few minutes later the job runs again. Shouldn't the job runner be captured any errors, so that unless the container restarts, all jobs should have an eventual status before running again?