Administration Guide

Jobs and Schedules

On this page

A job is work that the Automation Server runs on a schedule. Every job, of every kind, is part of one job catalog: scheduled workflow triggers, recurring tickets, and the jobs of the integrations and services. You schedule, run, enable, and disable jobs in the Settings App and in the Admin Center, and runs are recorded as sessions in the log of the job's kind.

Jobs in the Settings App

Find a job

Each job kind that runs a separate program has its own page in the navigation tree, beside a Logs node, and the Job List shows the jobs of every kind:

Job kind Page
Mail Connector E-mail Processing > Mail Connector
Active Directory Import Services > Active Directory Integration > Synchronization
Alloy Discovery Connector Services > Alloy Discovery Integration > Synchronization
AlloyScan Services > AlloyScan > Synchronization
Archiving Services > Archiving > Archiving
Reporting Services > Scheduled Reports > Reports
Scheduled Task Services > Scheduled Tasks > Tasks
All kinds Services > Automation Server > Job List

Trigger On Condition and Recurrent Ticket jobs have no page of their own and appear only in the Job List. The Archiving node is not shown on Azure SQL or in Alloy Navigator Cloud; see Administering Alloy Navigator Cloud.

By default, the Job List groups the jobs by kind and sorts them by name, and its columns show the name, the last run status, the next run date, and whether the job is enabled. The last run status reads "Succeeded", "Failed", "Running", or "Unknown", followed by " at <last run date>" when a run is recorded. "Unknown" stands for no recorded status or a run that is waiting to start. While the Job List is the page shown, it refreshes itself every 10 seconds by default.

Instead of a date, the next run date shows a message, the first that applies:

Message When
"Recurrence is disabled." A recurring ticket whose Create Action is no longer a recurrent action. The job stays in the list but never runs.
"Queued to run as soon as possible" A run request is waiting for the Automation Server.
"Queued for forced termination" A termination request is waiting for the Automation Server.
"The job schedule is disabled." The job is disabled.
"The job has expired." The schedule has run out.
"The job has not started yet." No next run is calculated yet.

On the Job List, the toolbar holds Open, Run, Terminate, and Refresh, and the right-click menu adds Run, Terminate, Enable, and Disable. Enable and Disable are on the right-click menu only. A job kind's page adds New, Delete, and Copy Item to the toolbar, Copy Item being enabled for one selected scheduled task; its right-click menu also holds Copy Job ID (GUID) to Clipboard, Enable, Disable, and Export Selected Settings.... On the grouped list, a focused group row counts as two rows, so the commands for one job are unavailable on it.

Open a job

Select one job and click Open. A job that runs a separate program opens its kind's window, a Trigger On Condition job opens the Trigger on Condition window, and a Recurrent Ticket job opens the Recurrent Ticket window.

Change a job's schedule

  1. Open the job.
  2. Click the schedule button of the job's window: Change in the Mail Connector and Alloy Discovery Synchronization windows, Change... in the Active Directory Synchronization, Archiving, scheduled task, scheduled report, and recurring ticket windows. In the Trigger on Condition window, the button is Change... beside the Use advanced schedule choice of the Check Condition: group.
  3. In the Schedule window, choose Daily, Weekly, Monthly, or Yearly under Occurs and fill in its panel.
  4. Under Daily frequency, choose Occurs once at: and a time, or Occurs every: with a number of Minute(s) or Hour(s) and the Starting at: and Ending at: times.
  5. Under Duration, set the Start date:, and an End date: or No end date.
  6. Click OK.

For the ranges and refusal messages of the Schedule window opened from a reporting job, see Scheduled Reports.

Run a job now

  1. On the Job List or on a job kind's page, select one job. Run is available while the page shows the Automation Server as running.
  2. Click Run.

When the request reaches the Automation Server, the service starts the run at once, unless it is not the active server or the job is already running or locked. A run started this way ignores the schedule and whether the job is enabled, so it also runs a disabled or expired job, and it does not change the next run date. It also goes ahead while the Automation Server has lost its own database connection, when a scheduled run would be skipped.

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." Any other failure shows "Cannot send request to the Automation Server. Make sure the Automation Server is configured and started."

Terminate a running job

  1. Select one job whose last run status is Running. Terminate is available for all job kinds except Trigger On Condition and Recurrent Ticket.
  2. Click Terminate, and confirm "Are you sure you want to terminate this job?".

The Automation Server stops the program that the job is running. 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." Any other failure shows "Cannot send request to the Automation Server. Make sure the Automation Server is configured and started."

Enable or disable jobs

IMPORTANT: On the Job List, do not select Trigger On Condition or Scheduled Task jobs together with jobs of other kinds to enable or disable them. The kind of the focused job decides where the enabled state is written, for every selected job.

  1. Select one or more jobs.
  2. Right-click the selection and choose Enable or Disable.

The list refreshes, and the Automation Server is told that the jobs changed.

The enabled state of a Trigger On Condition or Scheduled Task job is stored with its trigger or scheduled task, and that of any other job with the job itself.

Copy a job's ID and set its log level

On a job kind's page, Copy Job ID (GUID) to Clipboard copies the selected job's ID. To set a job's log level, type debug in the page's grid and confirm "Enable debug mode?". A log level column appears, and the right-click menu gains a Log Level command with Normal and Detailed.

Read a job's sessions

The windows of Archiving, Mail Connector, Active Directory Synchronization, Alloy Discovery Synchronization, AlloyScan Synchronization, Scheduled Report, Scheduled Task, Recurrent Ticket, and Trigger on Condition jobs have a Sessions tab with the job's own runs. The tab is disabled until the job is saved, and it refreshes itself while it is the active tab. The tab is the log browser of the job kind's log, limited to this job's runs, and it shows that log's columns.

  • View Log, or a double-click, opens the run's log text as a .log file in the program Windows uses for that file type.
  • Delete removes the selected sessions after "Are you sure you want to delete the selected record?" or, for several sessions, "Are you sure you want to delete <n> selected records?", and reports "<n> records have been deleted." afterwards.
  • Clear All asks "You are about to delete all entries from the Service Log. Are you sure you want to proceed?" and then removes every session of this job only.
  • Refresh reloads the list.

The tab has no Settings... command. The retention period is set on the log's own node under Logs (see Logs), where Clear All removes the sessions of every job of that kind, after "You are about to delete all entries from the Service Log. Are you sure you want to proceed?". Settings... there requires the permission to manage logs; without it, the Settings App shows "You do not have enough permissions to use this function." A log shows its newest 1000 sessions and says "Last <n> records are loaded".

Jobs in the Admin Center

Find a job

The job pages are in the Services and Integrations section, each behind its own permission: Active Directory Integration, Alloy Discovery Integration, AlloyScan, Scheduled Reports, Scheduled Tasks, and Automation Server. Mail Connector is under E-mail Processing. The Admin Center has no Archiving page; archiving jobs are configured in the Settings App, whose Archiving node is not shown on Azure SQL or in Alloy Navigator Cloud.

  • Automation Server has no tabs: its job list is shown directly under the page header, with the Automation Server's status above it. The list has no New and no Delete button.
  • Active Directory Integration has the tabs Synchronization, Domain Credentials, and Logs.
  • AlloyScan has the tabs Synchronization and Logs.
  • Alloy Discovery Integration has the tabs Conflict Policy, Conflict List, Synchronization, and Logs. Only Synchronization lists jobs.
  • Mail Connector has no page tabs.
  • Scheduled Reports has the sub-pages Reports, which lists the jobs and opens by default, and Logs.
  • Scheduled Tasks has no New and no Copy button. Its log is a page of its own beside the job list, not a tab of the job form.

On the Automation Server list, the next run 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 last run status shows None when no status is recorded, the status with its date when both are recorded, and nothing otherwise.

Open a job

Select one job and click Edit. The job's form opens on its Settings tab, which holds the schedule, and ends with a Sessions tab once the job exists. Active Directory, Alloy Discovery, and AlloyScan jobs add a Processing tab between them, and Mail Connector jobs add Processing and Preprocessing Rules.

From the Automation Server list, Active Directory, Alloy Discovery, Reporting, Scheduled Task, AlloyScan, and Mail Connector jobs open in their own forms. A job of any other kind shows "This feature is not yet available in the Admin Center. Please use the desktop Settings App for this task." and Close.

Change a job's schedule

Every job form holds the schedule as one field on its Settings tab. The field shows the schedule as a sentence, for example "Occurs every 1 day(s), at 12:00 AM, started 9/12/2026". A new Scheduled Reports or Mail Connector job starts on a monthly schedule: day 1 of every 1 month, once at 12:00 AM.

  1. Open the job, and click the edit (pencil) icon of the schedule field. The Schedule drawer opens.
  2. Under Occurs, choose Daily, Weekly, Monthly, or Yearly, and fill in its panel:
    • Daily: every 1 to 366 days.
    • Weekly: every 1 to 52 weeks, on at least one weekday. With no weekday, the drawer shows "You must choose at least one day of the week".
    • Monthly: a day from 1 to 31, or a relative day, of every 1 to 99 months.
    • Yearly: one or more months, and days of the month, or week numbers and weekdays. An empty list is refused with a message such as: The "Months" field is mandatory, it can't be left blank.
  3. Under Daily frequency, choose Occurs once at: and a time, or Occurs every: with a number of Minute(s) or Hour(s) and the Starting at and Ending at times. The number goes from 1 up to 1440 minutes or 24 hours. An Ending at time earlier than the Starting at time is refused with "Cannot be earlier than Start Time".
  4. Under Duration, set the Start date, and an End date: or No end date. The start date is required, and an invalid one shows "Date format is not valid". An end date earlier than the start date is refused with "Cannot be earlier than Start Date".
  5. Click OK.

The schedule uses the application server's time zone. When your local UTC offset differs from the server's, the schedule field shows "Server time (UTC<offset>)" below the schedule sentence, unless it shows a validation error or another helper text in its place. The Schedule drawer then shows the warning "The schedule uses the application server's time zone (UTC<offset>). Please note that the server time is <n> hours ahead of your local time." ("behind" when the server's time trails yours), where <n> is the difference in hours, for example 3 or 5.5. When your offset and the server's are the same, neither text is shown.

In Alloy Navigator Cloud, the Occurs every: number cannot go below the minimum interval of the job kind, and for a Scheduled Reports job it is disabled; see Minimum intervals in Alloy Navigator Cloud. For the schedule of a reporting job, see also Scheduled Reports.

Run, terminate, enable, or disable a job

  1. On the job's page, select the job or jobs.
  2. Click the command:
    • Run needs one selected job and an active Automation Server.
    • Terminate also needs the job's last run to be still running.
    • Enable and Disable act on the whole selection.
    • Delete is shown where the page offers it, for example on Scheduled Tasks and Scheduled Reports.

A run or termination requested in the Admin Center goes through the database, so the Automation Server can take up to one refresh interval to pick it up. On every job page, Run shows "Your job will be started as soon as possible, typically within a few minutes. Please check the job status later." in an Info window with Ok and Help. While the request waits for the Automation Server, the job's next run shows "Queued to run as soon as possible". As in the Settings App, a run requested this way ignores the schedule and whether the job is enabled, and it does not change the next run date. 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 instead of queuing it again. If a termination is already requested, it shows "Please wait, the job will be terminated soon." and refreshes the list.

The job lists of the Admin Center do not refresh themselves on a timer. A list is read again after Run, Enable, Disable, or Delete, and when you click the refresh icon. Only the Automation Server's status on the page is checked on a timer, every 60 seconds.

Read a job's sessions

Once the job exists, its form ends with a Sessions tab that lists the job's own runs, newest first.

  • View Log, or a double-click, opens the run's log.
  • Delete and Clear All are shown only to users with the permission to manage logs. Clear All removes the sessions of this job only. The Sessions tab of a scheduled task has neither command.
  • The tab has no Settings... command. A refresh icon is shown only on the Sessions tab of a Mail Connector job.

The columns depend on the job kind:

Job kind Columns
Active Directory Run Date, Job Name, Comments, Duration, Total Users, Created Persons, Updated Persons, Errors
Alloy Discovery Run Date, Job Name, Comments, Duration, Created Computers, Created Conflicts, Errors
AlloyScan Run Date, Comments, Created Computers, Created Hardware, Updated Computers, Updated Hardware, Duration, Errors, Job Name
Scheduled Task Run Date, Job Name, Duration, Errors, Comments
Reporting Run Date, Job Name, Report Name, Comments, Duration, Errors

Job kinds

Job kind What runs
Trigger On Condition A scheduled workflow trigger. Runs inside the Automation Server.
Recurrent Ticket A recurring ticket. Runs inside the Automation Server.
Mail Connector A separate program, started for each run.
Active Directory Import A separate program, started for each run.
Reporting A separate program, started for each run.
Alloy Discovery Connector A separate program, started for each run.
Archiving A separate program, started for each run.
Scheduled Task A separate program, started for each run.
AlloyScan A separate program, started for each run.

A job whose program was never installed on the Automation Server's computer fails when it starts, with "File not found".

A Trigger On Condition job exists while its trigger runs on a schedule, either "Every N minutes" or an advanced schedule; a new trigger starts at 5 minutes. Switching the trigger to "After the object has been saved" removes its job and also deletes the record of the objects the trigger has already acted on. The job and its trigger are always enabled or disabled together. Deleting a Trigger On Condition job also deletes its trigger, and deleting a Recurrent Ticket job also deletes its recurring ticket.

Technicians set up recurring tickets, with their schedule, in the Web App. In the Settings App, the Recurrent Ticket window of an existing recurring ticket changes only its schedule and whether it is enabled.

Background components record the changes they make under fixed service identities, which appear as the authors of the records: Automation Server, Mail Connector, Alloy Discovery Integration, Active Directory Integration, Archiving, Scheduled Reports, Self Service Portal, Import, Alloy Navigator API, Scheduled Task Agent, and AlloyScan.

Schedules

Every schedule, for a job, a trigger, or a recurring ticket, has the same three parts:

  • Which days: every N days, every N weeks on chosen weekdays, every N months on a day of the month or on a relative day, or in chosen months on days of the month or on chosen weekdays of chosen weeks. A relative day is the first, second, third, fourth, or last day, weekday, weekend day, or named weekday.
  • What happens on those days: one run at a time of day, or a run every N minutes or hours between a start time and an end time. A window whose end time is earlier than its start time runs past midnight.
  • For how long: a start date, and an end date or no end date.

How schedules behave:

  • After every scheduled run, the next run is calculated again. A run that takes longer than its interval gets a new next run, so a slow job does not build up a backlog.
  • A job that was due while the Automation Server was down runs once as soon as the service is active again. The run is recorded in its log.
  • When the next run would fall after the schedule's end date, the job stops and shows as expired.
  • A disabled job has no next run date. Enabling a job again or editing its schedule calculates the next run afresh and clears the expired state.
  • A job added, changed, or removed in the Settings App reaches the Automation Server at once.

A new Mail Connector job in the Settings App starts with a schedule of every 1 minute on-premises and every 5 minutes in Alloy Navigator Cloud.

On-premises, every job kind has a minimum interval of 1 minute, in the Settings App and in the Admin Center. The higher minimum intervals below apply only in Alloy Navigator Cloud.

Minimum intervals in Alloy Navigator Cloud

In Alloy Navigator Cloud, each job kind has a minimum interval. The Settings App enforces the minimum in the Schedule window. The Admin Center applies the minimum in the form and also rewrites the stored schedule when you save (for a Mail Connector job, only when the job is added), so for some job kinds the saved schedule differs from what you entered. See Administering Alloy Navigator Cloud.

Job kind Settings App Admin Center
Mail Connector 5 minutes, or 1 hour for an interval in hours 5 minutes. When a job is added, a shorter interval in minutes is raised to 5 minutes.
Active Directory Import 240 minutes, or 4 hours Any "every N" interval is set to exactly 240 minutes or 4 hours, longer intervals included.
Reporting 1440 minutes, or 24 hours Any "every N" interval is set to exactly 1440 minutes or 24 hours, longer intervals included. In the form, the Occurs every: count is disabled.
Alloy Discovery Connector 15 minutes for an interval in minutes A shorter interval in minutes is raised to 15 minutes.
AlloyScan 15 minutes for an interval in minutes A shorter interval in minutes is raised to 15 minutes.
Scheduled Task 60 minutes A shorter interval in minutes is raised to 60 minutes.
Archiving The Archiving node is not shown. An archiving job opened from the Job List is read-only. The Admin Center has no Archiving page.
Trigger On Condition, Recurrent Ticket 15 minutes for an interval in minutes Not edited in the Admin Center.

Job history

Each job shows its last run status and its next run date.

A run is recorded as one session in the log of the job's kind. A session holds the run date, the duration, a remark, the statistics that the job kind reports, and the text of the run's log.

  • Trigger and recurring ticket runs are logged by the Automation Server. A run that had nothing to do says so in its log.
  • The other job kinds log their own runs. When such a program ends with an error code, the Automation Server records the failed run and its error. A run that wrote nothing leaves no session.
  • A failed job is also written to the system log, with the job's name and its error.
  • Sessions older than the log's retention period, 30 days by default, are purged once a day. See Logs.
  • When you delete a job, its sessions stay in the log, no longer tied to the job.

To read a job's run history, open the job's Sessions tab, in the Settings App or in the Admin Center, or the log of the job's kind under Logs.