Job Scheduling and System Automation
adTempus 4 Known Issues
This page is for adTempus 4 only. For adTempus 5, see adTempus 5 known issues.
Open Issues
The following Knowledge Base articles describe known issues in the current adTempus 4 release. See the Release Notes for information on recently-fixed problems.
| Issue | Status |
|---|---|
| K00000617: Job execution on Agent fails with database error | Hotfix Available |
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.
Hotfix 4.9.2.23331
November 27, 2023
November 27, 2023
Agent logs database error for primary key violation when master sends a job to agent for execution
Erroneous duplicate login error when trying to add login that uses adTempus security
When you try to add a security login that uses adTempus (user ID/password) security, you may get an error that a login already exists for that user even though there is no existing login.
Attachments may not be included when email notification is retried after failure
When a Notification Action or Notification Task includes attachments that are not configured to be
saved in the job history, these attachments are not included if an email notification fails and is later successfully retried.
File Transfer task may behave incorrectly if source folder has a trailing slash
If a File Transfer Task is configured with a source folder that has a trailing slash (e.g., "c:\myfolder\"), the task may behave incorrectly, including:
- Failing to properly apply exclusions
- Failing to copy/move files from the source folder
Refinements to handling of system clock changes
Jobs can be configured to run if their scheduled execution is missed because the system's clock is set forward and/or to repeat if the clock is set back. This feature was intended to address small time changes such as clock synchronizations and Daylight Saving Time changes. It can cause problems in scenarios with larger time changes, such as on a computer where the system clock is incorrect by months or years at startup and is subsequently synchronized with a time source after adTempus has scheduled jobs for execution. To address these issues adTempus was modified to recalculate execution schedules (ignoring the settings for individual jobs) for forward clock changes of more than 4 hours or backward changes of more than 12 hours. That is, if the clock is set forward by more than 4 hours, no missed jobs will be executed; if the clock is set backward by more than 12 hours, any jobs that would normally execute in the "repeated" timeframe will be executed.
Script Host not returning values for some properties
When a script runs, the adTempus object is not returning values for these properties:
- JobOID
- JobInstanceID
- StepOID
- StepInstanceID;
- InstanceID
- StepNumber
File Trigger may miss first file created when monitoring folder that doesn't exist yet
If a File Trigger is configured to monitor a folder that does not exist when the trigger starts monitoring, the File Trigger may fail to trigger if the folder is created and files are immediately created in it.
Some links in the Welcome page are opened with IE rather than the default browser
This problem was fixed.
Resolved problem with erroneous clock change detection
In some cases where the adTempus server is under high load (server CPU at 100%) adTempus may incorrectly detect that the system clock has been set forward by a second or two. If this happens at the exact second that a job is scheduled to run, the execution may be missed if the job does not have the option set to "Run once if clock set forward."
Terminating a job with pending instances may lead to phantom active instances
If a job is executing and other instances of the job are pending execution (waiting for the active instance to complete) and you terminate all instances of the job, in rare cases this can result in a database error that causes adTempus to think there are still active instances of the job even though there are not; this can prevent additional instances from running if they are configured to wait for previous instances. This problem was corrected.
