Job Scheduling and System Automation
adTempus Beta
adTempus 6 adds many new features. See what's new.
If you have an adTempus 5.1 license it will work with the beta release. Otherwise you will be prompted to generate a temporary license during installation. After the beta period ends you will need a valid license.
Please report issues large or small using the support request form or discussion forum.
Installer
You must log in or register to download beta releases.
Release Notes
Following is the complete list of changes. For more details see What's New in the user guide.
Version 6.0.0-prerelease.1008
November 11, 2026
November 11, 2026
Web Request Task enhancements
The Web Request Task has been expanded from a simple page download into a general-purpose tool for calling Web services and APIs.
Preserve timestamp on download option added for cloud file providers and file transfer tasks
An option was added to cloud storage providers to preserve the file timestamp on download. When this option is selected, file operations that download from this provider will set the last write time of the local file to match the timestamp from the remote file. This option will default to selected for all new cloud storage providers but will not be turned on for existing providers, to ensure backward compatibility. The setting is configured on the Options page of the file service provider properties window.
The same option was added to File Transfer tasks. This can be used to enable the behavior for a specific task.
The timestamp is preserved if the option is enabled in either location.
New option to move Job Variables between job and steps
When editing a job, it is now possible to move Job Variables from the job level to a step, or from a step to the job. This option is found on the context (right-click) menu for job variables.
Added support for custom app credentials for OAuth
For email servers and file servers that use OAuth for authentication, adTempus now supports custom (user-created) application registrations instead of using the public applications created by Arcana Development. This allows OAuth authentication to be used in scenarios where organization policies prevent use of a public application registration.
Reduce database deadlocks
Changes were made to the adTempus database and code to reduce the occurrence of database deadlocks in busy instances.
Database Task has new option to save DataSet to CSV file
The Database Task previously allowed you to select data and save it in an XML file in .NET DataSet format. A new option allows you to save database query results to a CSV file instead.
Updated MySQL database driver
The database driver for Database Tasks that operate against MySQL has been updated to a new driver with wider database server support.
Added Job Execution Task to Job Diagram
Job Execution Tasks were missing from the Job Flow Diagram.
Updates to Job Diagram
The Job Diagram tool has been refreshed to resolve some usability issues (such as zooming and panning). The tool used to create the diagram has changed, and diagrams will look slightly different from those produced by previous versions.
Improvements to Web Console
The Web Console has been improved: it now runs as a self-contained web server process rather than requiring IIS installation, and it is included as part of the adTempus installation package. See the documentation.
Limit value length when writing variables to Job Detail Log
When Job Variables are written to the Job Detail Log they are now truncated to 200 characters. This limit can be configured using the "DebugLogging:MaxVariableValueLengthInVariableList" server option.
Fix HTML markup being written in Job Detail Log
Job Variables containing HTML markup were written to the Job Detail Log without escaping the HTML, causing formatting problems when viewing the log.
Export window enhanced to make it easier to export all data
The Export window now has an option to export all data that the user has permission for. This eliminates the need to explicitly select all of the objects in all of the categories.
Shared Scripts are not included in object snapshots
The full-system automatic snapshot created each day did not include Shared Scripts that are not referenced by any jobs.
Added support for custom OAuth endpoints for email
adTempus currently provides built-in configuration for connecting to Microsoft and Google mail servers using OAuth. New settings in the Messaging Service Provider allow the use of OAuth with other mail servers for which adTempus does not have built-in configuration.
Added support for OAuth authentication for Gmail and Google Drive
OAuth authentication can now be used with Mail Service Providers and File Service Providers that connect to Google services.
Permission error when updating job with Variable Update task
When importing a job with a Variable Update task, import may fail with a permission error on the target job or group even though the user has permission to update it.
New adTempus PowerShell module
adTempus now has a PowerShell module exposing operations such as executing jobs and exporting/importing data.
Improved job identification and navigation in Alerts and Message Log Query views
The Alerts and Message Log Query Views have been updated to include the Group name and Queue name as optional columns (right-click a column heading for a list of available columns to display).
"Go to Job" and "Edit Job" commands have been added to the context (right-click) menu in these views.
Job Properties window now displays Group name
The Job Properties window now shows the name of the Group the job belongs to.
State data for File Trigger moved from disk to database
For File Triggers, adTempus stores data about what files have previously been seen by each trigger so that the state of the trigger can be restored after a restart of adTempus. This data was previously stored on disk, which prevented restoring the state when failing over to a backup instance, potentially resulting in missed or duplicate triggers. State data will now be stored in the database instead to avoid this problem.
In situations where file triggers are monitoring targets with very large numbers of files, this state data can grow very large. In such cases, and where state preservation during failover is not needed, it may be desirable to revert to the previous behavior. This can be done by setting the advanced server option "FileTrigger:SaveStateToDatabase" to "false".
Removed support for notifications using Jabber (XMPP) instant messaging
This feature was removed
Changing Engine Mode between standalone/controller modes and agent modes no longer allowed if data is present
New validations prevent changing the Engine Mode of the adTempus Server from Standalone/Controller to an Agent mode or vice versa if jobs have already been created. Switching modes can lead to inconsistent data and other problems.
Added ability to export Security Logins and Roles
Security Logins and Roles are now listed in the Export window, allowing you to export them explicitly. Previously logins and roles were only exported if they were linked to other objects being exported.
New Response Events for Completed with Errors and Completed with Warnings statuses
Version 5.1 introduced the Completed with Errors and Completed with Warnings job statuses but did not add new events to allow Responses to be triggered by these states. This version adds new events, along with options to determine whether these states should also trigger Responses that use the Job Succeeded or Job Failed events.
ODBC connection support added to Database Operation Task
The Database Operation Task was enhanced to support data sources for which an ODBC driver is available.
Added support for async user scripts
User scripts written in C# and VB.NET can now override UserScriptBase.RunAsync instead of UserScriptBase.Run if your code needs to perform async operations.
Improved error handling for trigger selection scripts
Functionality has been improved for user scripts used to evaluate trigger conditions. Trigger selection scripts can now use the ReportProcessingFailure method to report script processing errors that should be communicated to the user or cause the script to be temporarily disabled, but that should not cause the trigger to be disabled until it is manually re-enabled, as is the case if a script throws an exception.
A new server-level option ("JobManager:FailedTriggerScriptSuspensionTime") has been added to allow override of the trigger suspension time when triggers do fail with an exception. This can be used to set a temporary suspension rather than the default behavior of waiting until the trigger is manually re-enabled.
New option to suspend evaluation of some triggers during Exclusion Periods
A new option was added to some triggers to determine whether the triggers continue to be evaluated during Exclusion Periods. The option was added to the File Trigger, Email Trigger, and Computer Monitor.
Added session keepalive option for FTP transfers
A new "Send keepalive commands" option was added to the settings for FTP servers. This option can be used to prevent firewalls or routers from dropping control session connections during a long file transfer, which causes the transfer to fail with a timeout error.
Added support for PowerShell 7 scripts
The adTempus script host was enhanced to support PowerShell 7+ scripts in addition to Windows PowerShell (5.1) scripts. See documentation.
PowerShell scripts now use system-provided host
PowerShell and Windows PowerShell scripts are now executed using the corresponding system-provided host process (pwsh.exe or powershell.exe) rather than the adTempus script host. This ensures that scripts will always use the same PowerShell version and behave the same as scripts run outside of adTempus.
Updating Linked Server causes unexpected error if Console is not connected to both servers
If you edit a Linked Server in the Console while the Console is not connected to that server, clicking OK causes adTempus to display an unexpected error reporting window, with error "Value cannot be null. Parameter name: otherServer".
Fixed "invalid import settings" error when importing file with password set
When you attempt to import an export file that is protected with a password, adTempus returns error ADT005215E: "Invalid import settings: the specified
encryption type does not match the encryption type used to create the
file." This problem was fixed.
Added support for SharePoint for file monitoring and file transfers.
adTempus now supports SharePoint for File Triggers and File Operation Tasks.
Improved performance for email triggers and tasks when using IMAP connections to mailboxes with a large number of messages
Due to inefficient processing, processing mailboxes with many thousands of messages previously took a long time to complete on each processing pass. Message filtering has been greatly improved to eliminate this performance issue.
Also as part of this change, adTempus now looks only at messages from the last 7 days the first time it connects to the mail server for a new trigger or task, in order to limit the amount of processing required.
EmailProcessing.MessageLocation job variable contains wrong filename
When an email processing task saves a message to disk in RFC822 format it stores the wrong filename in the "EmailProcessing.MessageLocation" job variable, so user scripts do not have access to the filename.
Added Markdown support in extended text fields
Extended text fields such as Notes and Descriptions now support Markdown formatting. These fields now have a formatting toolbar and the capability to display a preview of rendered Markdown.
Cannot view step details on Job Accounting Report
Clicking an instance does not expand the instance to show the step details.
Reset seen-message tracking when incoming mail provider is changed to a different IMAP server
When an email trigger or email processing task uses an IMAP server, each trigger or task keeps track of which messages it has already seen. If the Messaging Provider is changed to point to a different IMAP server, this tracking information is no longer accurate (because it is specific to the server) but adTempus does not recognize this. This can lead to new messages being skipped or old messages being reprocessed. adTempus was changed so that if the server address is modified, the user is asked whether message tracking information should be reset.
Import fails with large amounts of data
When attempting to import a large amount of data from an export file the Console connection to the server may time out, causing the connection to fail and the import to abort. This may happen during the import process when the "Save all imported objects if no problems are found" or when you click "Save All" after reviewing objects to be imported. This problem was corrected so that the connection does not fail.
Improved error handling for email triggers
Email triggers have been enhanced to improve error handling. Email triggers now retry transient errors such as network problems and temporarily unavailable mailboxes. Trigger status and error conditions are reported more clearly, and common problems no longer cause the trigger to be disabled (requiring manual re-queueing of the job).
Improved reporting for trigger problems
adTempus has been enhanced to more effectively report problems with triggers (such as configuration problems, connection problems, login problems, etc.)
- The number of scenarios in which a trigger is disabled (forcing a manual requeueing of the job) have been reduced.
- When problems occur, a warning message is now reported in the Trigger Status for the job, and the job status is set to the new value of "Trigger Warning."
- For more severe problems, or when a warning condition goes unresolved after several retries, adTempus now writes an error Alert to the Job Log for the job (appears in the job history and in the Alerts view in the Console) and sets the job status to the new value of "Trigger Error." Additionally, a new "Trigger Error" Response Event now allows notification responses to be triggered to inform operators of the problem.
- When a problem prevents adTempus from continuing to evaluate the trigger, the previous behavior still applies: trigger is disabled, an error Alert is written tot he Job Log, and the "Trigger Failed" Response Event is fired.
Added support for scripts using .NET 10
The adTempus scripting framework has been updated to support scripts using .NET 10 in addition to the existing support for .NET Framework. A new Framework option in the Script Editor specifies which framework to use.
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.
When Database Task sends data to a script for evaluation, script execution fails if the amount of data is large
When a Database Task is configured to collect data in a DataSet and send the DataSet to a script, execution of the script may fail with error "Failed to dispatch task or script for execution" if the DataSet contains a large amount of data. The problem was corrected.
