Article ID: CR00007269
Last Updated: February 9, 2017
Applies To
- adTempus 4 Fix available in release(s): Hotfix 4.4.0.17055 (March 1, 2017), 4.5.0 (January 13, 2018)
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.
Availability
This article describes an enhancement or bug fix included in the specified release(s). See the software download page to download the latest public release. For items included in a hotfix, see the hotfix download page.