Skip to main content

Results

Tracking Jobs: Monitor and History

Once a Job is submitted, your next question will naturally be: "Did it work?" In JAMS, tracking your automation is divided into two distinct areas depending on whether the Job is happening right now or if it happened in the past. Understanding the difference between the Monitor and the History is essential for troubleshooting and managing your daily workflows.

The Monitor​

Think of the Monitor as your active control room. If you want to know what JAMS is doing, you look at the Monitor. When an instance of that Job runs, it is displayed in the JAMS Monitor as an Entry. You can view Entries that are currently executing, waiting to execute, as well as Entries that have completed recently. By default, Entries will remain in the Monitor view for 10 minutes after completion, but you can configure this value based on your needs.

The Monitor is actionable: Because these Jobs are active, this is where you can intervene. If a Job is stuck, you can cancel it. If a Job is waiting, you can force it to start immediately by bypassing its dependencies.

History​

History provides detailed information for all Job executions that have completed in the Monitor. For each Job, you can review its run history, duration, the Agent it ran on, and whether it completed successfully or resulted in a failure.

You can also:

  • Submit a Job to run in the Monitor.
  • View the Properties of an Entry.
  • View the execution details and log file of an Entry to get more information for troubleshooting.
  • Query and filter the listed Entries based on your preferences.

You do not need to actively watch the Monitor to track your workflows. JAMS can proactively notify you via email when a Job finishes, or automatically trigger a recovery Job if something goes wrong. These automated responses are configured directly on the Job itself rather than in the Monitor, which we cover in detail in the Orchestration section.

Using the Monitor

Watch Entries that are running, waiting, or finished within the retention window.

History

Every execution that has completed, with its duration, the Agent it ran on and its outcome.

Events and Notifications

Send mail or run a recovery Job when a Job finishes.

Orchestration

Composing Jobs that depend on each other.