Description

Due to an issue with the way jobs are loaded at service startup, it was possible for the server to mark a job instance as "Abandoned" even if it had been triggered since the service start. This produced a secondary issue where the server thought the instance was still running even after it finished, preventing the execution of new instances of the job in cases where the queue or job was configured to limit concurrent instances.