Managing all Automation Server jobs

The Automation Server is Windows service dedicated to running various automated tasks that you define in Alloy Navigator Express. The Automation Server runs on the computer where you installed it, and it is configured separately using the Alloy Automation Server Manager.

ClosedClick here to view types of automated jobs that the Automation Server is able to run.

Automation Server properties

In the Services > Automation Server section, at the top, you can view the server properties:

  • Host - the computer name of the machine, which has the registered Automation Server instance installed.

  • Status - the status of the Automation Server, either Stopped or Running.

  • Version - the version of the Automation Server.

  • Audit Tools Version - the version of the installed Audit Tools.

NOTE: To start the Automation Server, use the Alloy Automation Server Manager. For details, see Starting and stopping the Automation Server.

Automation Server job list

In the Services > Automation Server section, in the grid, you can view all existing jobs, grouped by type. Each entry in the job list displays Closedbasic information about a particular job.

  • Job Type - displays the type of the job: Mail Connector, Recurrent Ticket, Trigger On Condition, etc.

  • Name - displays the job name and the job ID (where available).

    NOTE: The auto-generated ID uniquely identifies each workflow item, such as a Trigger or Create Action. For details, Accessing a workflow item or component by its ID.

  • Last Run Status - displays the status, date, and time of the last run of the job. Status can be one of the following:

    • Unknown - the job has not been loaded to the Automation Server yet or its schedule is disabled.

    • Running - the job is running at the moment.

    • Succeeded - the job was successfully completed.

    • Failed - the job failed.

  • Next Run Date - displays the date and time of the nearest scheduled job execution or either of the following messages:

    • The job has not started yet - The job is scheduled, but has not been run yet.

    • The job has expired - There are no scheduled executions before the end time defined for the job.

    • The job schedule is disabled - Running the job by schedule is disabled.

    • Queued to run as soon as possible - the job has been forced to run on the remote Automation Server. This message appears when your Automation Server instance is installed on a remote computer which does not belong to the same domain or workgroup as your Settings App. Typically, the remote Automation Server runs “ASAP” jobs within a minute after they were forced.

      NOTE: If the Next Run Date value differs from the due time in the job’s schedule, it may take up to a minute for the Next Run Date value to be updated.

  • Enabled displays if the job schedule is currently enabled.–

You can perform the following tasks in the job list:

  • ClosedTo refresh the job list:

    • The information displayed in the job list automatically refreshes every ten seconds. If needed, you can refresh it manually by clicking Refresh (or pressing F5 on the keyboard).

  • ClosedTo disable or enable a job:

    • Right-click the job and choose Disable from the pop-up menu. You can re-enable it by choosing Enable.

  • ClosedTo force a job to run:

    • Select the job and click Run on the Module menu. The job will run regardless of its schedule and disabled / enabled status.