Scheduled Tasks
On this page
A scheduled task is a workflow program that runs on a schedule, against no record. It has no target class, and no condition, form, template, or roles. This makes scheduled tasks the product's way to run integration and maintenance work rather than automation of single records. The workflow items themselves are described in Workflow Overview.
Each scheduled task is also a job of the Scheduled Task kind in the Automation Server's job list. You create and program tasks in the Settings App. In the Admin Center you edit, run, enable, and delete existing tasks and read their log. The Scheduled Task Agent can also run a task from the command line.
Scheduled tasks in the Settings App
Tasks are listed at Services > Scheduled Tasks > Tasks. The Services > Scheduled Tasks branch, with its Tasks and Logs nodes, requires the permission of the Scheduled Tasks branch. The ID column shows the task's workflow item number. The page's commands are New, Open, Delete, Copy Item, Enable, Disable, Run, Terminate, and Copy Job ID (GUID) to Clipboard.
Create a task
- Go to Services > Scheduled Tasks > Tasks and click New.
- On the Settings tab, fill in Name:, Description:, and Group Name:.
- Under Schedule, click Change..., set the schedule in the Schedule window, and click OK.
- Select or clear Enabled.
The task's operations are on the Programming tab; see Program a task.
Copy Item copies the selected task under a new ID and opens the copy.
End a task with Return or Abort
Use Return to finish the task early and save the changes made so far. To finish successfully without saving those changes, configure it in the Settings App:
- Open the task's Programming tab and select the position for the step.
- Click New > Return.
- Select Discard all changes. Clear the check box when changes should be saved.
- Leave Enable operation selected and click OK.
With the check box selected, the tree shows Return (discard all changes). The option is available in the task's own program; it is not offered inside an embedded Create Object or Act on Object block for another object class. It is also not a named function's return-value setting.
Use Abort when the task must stop without saving pending changes and be reported as Failed. For the scope of the discarded changes, messages, and log entries, see Return and Abort results and Abort.
Program a task
On the Programming tab, you add each step from the operations tree's New menu. The menu lists the operations in groups:
- Update Field, E-mail Notification, Push Notification, Execute Function, Create Object, Act on Related Object, Relate To, Unrelate, External Command, Message Box, Execute SQL, and Add Attachments
- Break, Return, and Abort
- Declare Variable, Set Variable, Iterate Collection, and Iterate String List
- Comment
- "IF" Group, "ELSE IF" Group, and "ELSE" Group
Depending on the workflow object, some of these operations are hidden or unavailable. For a service workflow object, Act on Related Object reads Act on Object. Break is available only inside a loop.
- On the Programming tab, select the row after which the new step goes. When the selected row is an IF, ELSE IF, or ELSE group, the new step becomes the first row inside it.
- Click New and choose the operation.
- Break and Abort are added at once, without a window.
- Comment opens its own comment editor.
- Create Object and Act on Related Object first ask for the object.
- In the operation's window, set the step's values. The window's caption is the operation's name, and its header shows Object Class: with the class the step works on. Inside a Create Object or Act on Related Object block, the header shows that block's class and a line that says how it is created from or related to the workflow object.
- Leave Enable operation selected, or clear it to save the step disabled. A run skips a disabled step.
- Click OK, or click Cancel to remove the new row again.
OK stays unavailable until the step's required values are set. While Enable operation is selected, OK refuses a step whose check fails and shows the reason; selecting Enable operation shows the same reason. For an E-mail Notification step with a parameter left unassigned, the reason is "This operation can not be executed, because not all parameters of the notification are assigned."
To turn off a step, or a whole IF, ELSE IF, or ELSE block, without deleting it, use the operations tree's Disable Operation command; Enable Operation turns it on again. A comment, an END IF row, or a selection that mixes enabled and disabled rows cannot be turned off or on this way.
What each operation does is described in Operations Reference.
Run, stop, enable, or disable a task
- Run runs one selected task now, while the page shows the Automation Server as running. When the Settings App cannot reach the Automation Server directly, the request goes through the database, and the Settings App shows "Since your Settings App and the Automation Server are installed on separate computers, it may take some time to test your settings. Please wait until the job has completed, and then check the session log to make sure that it runs as expected."
- Terminate stops one selected task whose last run status is Running, after "Are you sure you want to terminate this job?". When the request goes through the database, the Settings App shows "Please wait, the job will be terminated soon. Since your Settings App and the Automation Server are installed on separate computers, it may take some time to complete."
- Enable and Disable act on every selected task. The list then refreshes, and the Automation Server is told that the tasks changed.
When Run or Terminate fails for any other reason, the Settings App shows "Cannot send request to the Automation Server. Make sure the Automation Server is configured and started."
The Automation Server starts a requested run at once, out of schedule, unless the Automation Server is not active, or the task is already running or locked.
Delete a task
Select one or more tasks and click Delete. A system task is refused with "This is a system record and it cannot be deleted.", and the other selected tasks are deleted.
Read the Scheduled Tasks log
The log opens from Services > Scheduled Tasks > Logs, which requires the permission of the Scheduled Tasks branch, and from Logs > Scheduled Tasks, which requires the permission to browse logs. Each session carries the run date, the remark, the duration, the number of errors, the task's name, and the text of its log.
- View Log, or opening a session, shows the session's text.
- Delete removes the selected sessions.
- Clear All deletes every session of the log, after a confirmation.
- Settings... sets how long sessions are kept. It requires the permission to manage logs; without it, the Settings App shows "You do not have enough permissions to use this function." See Logs.
Refresh (F5) reloads the page, and the log also reloads itself while its page is shown. For the Sessions tab of a task's window, see Jobs and Schedules.
Change the schedule of a recurring ticket
For setting up recurring tickets, see Recurring Tickets; for the Recurrent Ticket window, see Jobs and Schedules. Recurring tickets have no page of their own in the Settings App; they appear only in Automation Server > Job List. The recurring ticket's Change... button opens the same Schedule window.
In Alloy Navigator Cloud, the Settings App's Schedule window accepts an interval in minutes of no less than 15 minutes for a recurring ticket. See Administering Alloy Navigator Cloud.
The run log of all recurring tickets is under Logs > Recurrent Tickets, for users with the permission to browse logs. See Logs.
A Create Action whose Available for: setting is Recurrent Tickets only or Regular and Recurrent Tickets has a Sessions tab, which lists the sessions of every recurring ticket built on that action. The tab is unavailable until the action is saved.
The Scheduled Task window
The Scheduled Task window has three tabs:
- Settings: Name:, ID:, Description:, Group Name:, the Enabled check box, and a Schedule group whose Change... button opens the Schedule window. A new task's group name is "Integrations".
- Programming: the task's list of operations. The operations are described in Operations Reference.
- Sessions: the task's runs.
A system task opens view-only and shows "This is a system task that cannot be modified. To view all details or make changes, create a copy of the task."
While the Automation Server is not running, the window shows "Warning. For this job to be executed, the Automation Server must be set up and running."
The Schedule window
In the Settings App, every job's editor opens the same Schedule window, the scheduled task's and the recurring ticket's included. Under Occurs, choose Daily, Weekly, Monthly, or Yearly; each has its own panel:
- Daily: Every N day(s).
- Weekly: Every N week(s) on:, with the days Monday to Sunday.
- Monthly: a day of the month, or a relative day (First, Second, Third, Fourth, or Last, and Sunday to Saturday, Day, Weekday, or Weekend Day), of every N month(s).
- Yearly: Months:, with Days: or On:.
Below the panel, Daily frequency holds Occurs once at: or Occurs every: N Minute(s) or Hour(s), with Starting at: and Ending at:, and Duration holds Start date:, and End date: or No end date. Close the window with OK or Cancel. The window enforces each job's minimum interval; for scheduled tasks, see Schedule limits.
Scheduled tasks in the Admin Center
The Scheduled Tasks page has a Tasks tab and a Logs tab. The page has its own permission; see Permissions Reference.
The Tasks tab lists the tasks with the columns ID, Name, Group Name, Last Run Status, Next Run Date, and Enabled. Next Run Date shows "Queued to run as soon as possible", "Queued for forced termination", "The job schedule is disabled.", "The job has not started yet.", or the date. The list has no New and no Copy button.
Open a task
Click the task's name, select one task and click Edit, or double-click the task. The task opens in a panel on its Settings tab, which holds the schedule; the Sessions tab lists its runs, and a session opens its log. The panel has no Programming tab.
While no Automation Server is active, the panel shows "Warning. For this job to be executed, the Automation Server must be set up and running."
The address of an open task contains the task's job ID, the ID that Copy Job ID (GUID) to Clipboard copies in the Settings App, without braces. The ID column of the list shows the workflow item number, not this ID.
Run, stop, enable, disable, or delete a task
- On the Tasks tab, select the task or tasks.
- Click the command:
- Run needs one selected task and an active Automation Server.
- Terminate also needs the task's last run to be still running.
- Enable and Disable act on the whole selection.
- Delete deletes the selected tasks.
If a run is already queued, the Admin Center shows "Please wait until the job has completed, and then check the session log to make sure that it runs as expected." and refreshes the list; if a termination is already requested, it shows "Please wait, the job will be terminated soon." and refreshes the list.
Read the log
The Logs tab shows the Scheduled Tasks log, with a settings page for how long sessions are kept. The same log is also in the Admin Center's Logs area. See Logs.
Run a task from the command line
The Scheduled Task Agent can also be run by hand. It is a console program
titled "Alloy Navigator Scheduled Task Agent", in the bin folder of the
Scheduled Tasks feature's installation, and its usage is:
ScheduledTasks.exe /AccessKey="Key_Name" /RunID="Job_GUID" [/Log="File_Name"]
/AccessKeynames a Database Access Key stored in the computer's registry./RunIDis the task's job ID, the one that Copy Job ID (GUID) to Clipboard copies. The usage text writes it in braces, for example/RunID={4253CC46-9DCF-4E6C-9C0B-C05E59ABD6AB}./Lognames the temporary log file, without an extension. Without it, the agent picks a random name.
Started without parameters, or with /? as the first parameter, the agent
prints its title, the copyright line, and its usage, and does nothing else.
Without /RunID, the agent does not start a run. A key that cannot be read,
or an ID that belongs to no task, stops the run with an error. A run started by hand appears in the Scheduled
Tasks log under the task's name.
Run a task with Windows Task Scheduler
To run a scheduled task on a schedule without the Automation Server, for example in Alloy Navigator Cloud when the task needs resources in your own network, schedule the Scheduled Task Agent in Windows Task Scheduler.
Before you begin:
- Choose a server computer in your network that can reach the SQL Server hosting your Alloy Navigator database and the local resources the task needs. The Scheduled Task Agent must be installed on it, and the Database Access Key imported. In Alloy Navigator Cloud, the agent comes with the Administrative Tools package; see Get Started with Alloy Navigator Cloud.
- Get the task's job ID. In the Settings App, go to Services > Scheduled
Tasks > Tasks, right-click the task, and click Copy Job ID (GUID) to
Clipboard. In the Admin Center, open the task and copy the ID from the
browser's address bar; the address holds it without braces, so enclose it in
braces for
/RunID.
To create the Windows task:
- On that computer, open Task Scheduler, for example by typing Task Scheduler in the Windows search box. If Windows asks for an administrator password or confirmation, provide it.
- Optionally, to keep your tasks apart, right-click Task Scheduler Library, click New Folder, and name the folder.
- In the Actions pane, click Create Basic Task.
- Type a name for the task and, optionally, a description, and click Next.
- Click Daily, Weekly, Monthly, or One time, click Next, set the schedule, and click Next.
- Click Start a program, and click Next.
- Click Browse, select
ScheduledTasks.exein theBinfolder of the installation, enter the/AccessKeyand/RunIDparameters, and optionally/Log, as the program's arguments, and click Next. For the parameters, see Run a task from the command line. - Click Finish.
The account that runs the Windows task must have sufficient rights to the resources that the scheduled task works with. To run the Windows task under a dedicated account, open its properties, and on the General tab, under Security options, click Change User or Group.
How a scheduled task runs
For each run, the Automation Server starts the Scheduled Task Agent, a separate program. The agent loads the task, runs its program under the Scheduled Task Agent identity, saves the records the program changed, and exits.
How a run ends:
| When the program | What happens |
|---|---|
| Ends with Return | Pending changes are saved; the job is Succeeded. |
| Ends with Return and Discard all changes | Pending changes are not saved; the workflow log is written and the job is Succeeded. |
| Aborts | The session log records the abort as an error. The agent exits with code 5, and the Automation Server marks the job Failed and records a job-failure entry in the System Log. |
| Fails with any other error | The error is also written to the system log. |
Whenever the agent ends with an error code, the Automation Server records the run as failed.
Each run is recorded as a session in the Scheduled Tasks log, whether it
succeeded, was aborted, or failed. During the run, the agent writes its log to
a temporary file in %ALLUSERSPROFILE%\Alloy Software\<product>\Logs\Services,
starting with the command line (without passwords), the version,
and the time zone of the computer. At the end, it adds "End of log", uploads the
file as the run's session, and deletes the file. A run that wrote nothing
leaves no session. The file stays on disk only when the run ended before its
connection settings were loaded, for example because the Database Access Key
could not be read, or when the upload failed.
The agent needs the Alloy Logging Engine; without it, the run stops before anything else happens. If the Scheduled Tasks feature was never installed, the run fails at launch with "File not found".
Schedule limits
On-premises, the Settings App accepts an interval of 1 minute or more for a task's schedule. In Alloy Navigator Cloud, the Settings App refuses an interval under 60 minutes, or under 1 hour when the interval is in hours, and the Admin Center raises an interval in minutes that is under 60 to 60 minutes. See Administering Alloy Navigator Cloud.
Supplied scheduled tasks
This section describes what a new 2026.1 Alloy Navigator database created with the Default Workflow contains; see Default Workflow Configuration. An upgraded database need not have these tasks, and an administrator may have changed them.
In the supplied configuration, every task is disabled, so none of them runs until an administrator enables it.
| Group | Task | Schedule in the supplied configuration |
|---|---|---|
| Maintenance | Maintenance: Delete 'x' Year Old History | Monthly, on day 1 at 01:00 |
| Maintenance | Maintenance: Delete 'x' Year Old Attachments | Monthly, on day 1 at 01:00 |
| Maintenance | Diagnostic: System Health Check | Every week on Sunday and on Monday at 09:00 |
| Maintenance | Integrity Check, and Index and Statistics Maintenance | Every week at 01:00 |
| Integrations | Adobe License Management, NinjaOne Integration, Microsoft Intune Integration, Microsoft Azure AD Integration, Microsoft SCCM Integration, Dell Warranty | Daily at 01:00 |
| Integrations | Availability Monitoring Device Checking | Every 10 minutes, all day |
| Integrations | Availability Monitoring Failed Devices | Every minute, all day |
| Integrations | AI Search Index Maintenance | Every hour |
For the integration tasks, see Integrations Overview.
Related topics
- Service Actions and Field Mappings
- Recurring Tickets
- Operations Reference - the operations a task's program can run.
- Integrations Overview
- Microsoft Intune
- Microsoft SCCM/MECM
- Dell Warranty
- Adobe License Management
- Microsoft Entra ID Import