Job Scheduling and System Automation
adTempus 5 Known Issues
This page is for adTempus 5 only. For adTempus 4, see adTempus 4 known issues.
Open Issues
The following Knowledge Base articles describe known issues in the current release of the software. See the Release Notes for information on recently-fixed problems.
| Issue | Status |
|---|---|
| K00000650: Assembly references not shown or saved for .NET scripts | Hotfix Available |
| K00000644: Setup fails to recognize valid license | Open |
Available Fixes
The following issues have been resolved in a hotfix update but have not yet been included in a general release. If you are affected by one of these problems, see the hotfix page to obtain the hotfix.
Version 5.1.2.8
Installer sets Engine Mode incorrectly
During installation, the installer may set the adTempus Engine Mode (Standalone/Controller, Agent, Agent-Only) incorrectly.
Jobs with mutual Job Conditions may deadlock
When two jobs have Job Conditions on each other using the "Job must not be running" rule, the jobs may deadlock waiting for each other, causing the conditions to time out or fail for both jobs.
Go to Job and Find keyboard shortcuts do not work when Console is first opened
When the Console is started, the Go to Job and Find keyboard shortcuts do not work until the Tools menu has been displayed at least once. The problem was corrected.
Resubmitted jobs may not execute if adTempus is restarted before execution begins
If a job is abandoned because it is running when adTempus shuts down, based on the recovery options for the job adTempus may restart the job when adTempus starts up again. When this happens, the old instance has a status of "Resubmitted" and a new instance is created to continue the execution. However, if adTempus is interrupted during its startup phase (e.g., adTempus is shut down again or the computer is restarted) before the new instance begins execution, the new instance is lost and the job does not restart. This problem was corrected so the job will be properly restarted even if the restart process is interrupted.
Version 5.1.2.7
Improved error reporting for OAuth2 connections
Errors with OAuth2 authorization often lacked specific details of the problem. This has been fixed to provide more detailed error messages,
Email processing produces duplicate key error on UQ_NotificationRecipientName when saving OAuth2 token
adTempus may log a database error regarding a duplicate key violation of constraint UQ_NotificationRecipientName while processing an Email Processing Task or Email Trigger that uses OAuth2 authentication for the mail server.
Version 5.1.2.5
Improved error handling in email triggers
Error handling in email triggers was improved so that transient errors (like network problems) are reported in the Trigger Status and do not cause the trigger to be disabled.
