AutoSys v24.1 Monitoring: A Flow-First Makeover for Real-Time Control

October 13, 2025

AutoSys v24.1 turns Monitoring on by default, with a landing page that lists saved Views at sign-in.

The new Flow tab shows jobs in a selected View, dependency, and status on one canvas; status styles, filtering, zoom, and orientation tools guide triage without menu hopping.

Preferences persist after logout, so each shift picks up exactly where the last left off. Right-click controls and the Advanced Send Event dialog simplify actions like Change Status or future-dated force starts. Regex search and Log Diff are available for log analysis.

A tabular Job Definition view, a per-job Alarms tab, and a “Has Help Desk Ticket” column with ticket numbers in Run details keep critical details close and traceable.

Together, these updates support day-to-day efficiency.

Why the Web UI Needed a Re-Think

Monitoring entered its modern phase in v24.0, but administrators first had to flip a setting in the application-access policy before anyone saw it.

That release introduced a landing page listing every saved view and, after selecting a View, showed its jobs, and clicking a job opened the job summary and details. User preferences persisted after logout, and development continued in an iterative manner.

The stated objective of the project is clear: simplify and enhance the UI so operator personas perform day-to-day activities efficiently. 

Version 24.1 moves that objective forward by enabling the monitoring capability by default and continuing the feedback-driven development cycle highlighted in each demo.

Within the refreshed interface, status styles provide quick filters, breadcrumbs improve navigation, and log Diff plus regex search support analysis. A click on any view now reveals all related jobs, while a second click exposes job runs, logs, starting conditions, and both JIL and tabular definitions.

Flow Tab – Your Entire Job Stream on One Canvas

The upgraded Flow tab displays job cards from the selected View onto one scrollable canvas, then color-codes them so status pops at a glance: green for success, blue for running, red for failure, and orange for waits. 

A quick glance at each card also reveals job type and, when relevant, badges for resources or globe icons for global variables. Logical links stay visible, so an AND reads as an AND.

Navigation remains smooth. Zoom controls, mouse scroll, and a small mini map keep large views in check, while an orientation toggle flips the layout between vertical and horizontal to match the task. Pan and selection happen together; drag to move, drag-select to pick multiple nodes.

On the left, a live filter trims the noise, dims non-matches, and offers a “Select all” option for bulk actions such as Change Status or Force Start. Need detail? Expand or collapse box jobs with a single click – or double-click if that feels faster. 

The result is one pane that turns sprawling dependencies into an ordered, actionable picture.

Job-Centric Drill-Downs that Cut Noise

First, the refreshed Job Summary page brings runs, regex-enabled logs, starting conditions, the complete job definition, and a JIL view into one panel. The new Log Diff option lets teams compare log versions side by side, making pattern checks straightforward.

Next, Job Definition data is presented in a tabular view. Expand or collapse any attribute (envvars included) and tap the help icon for field details. Attributes remain visible with expand/collapse controls and inline help.

The Alarms tab adds another layer of clarity. Filter, sort, or export MINRUNALARM and JOBFAILURE records directly from the job view. When an alarm opens a Help Desk ticket, the Has Help Desk Ticket column marks the run, and ticket numbers appear in run details.

Finally, from the Flow list or job views, open or edit a job, or launch Advanced Send Event to schedule a future status change.

Built-In Governance: Help Desk Ticket Association

Operators confirm ticket creation without leaving the console.

The Job Runs grid adds a Has Help Desk Ticket column that shows Yes when a run includes a ticket; selecting the run opens details listing each ticket number produced by alarms such as MINRUNALARM and JOBFAILURE. This keeps ticket information next to execution data.

The column stays hidden until users enable it through Choose Column, letting teams surface it when audits request proof. After activation, the column displays Yes only for runs with associated tickets on servers that support the feature.

AutoSys versions earlier than 24.1 show a different label (for example, “any”), and the run details list the ticket numbers, so historical information remains available. Ticket data appears at both grid and run level inside the Monitoring UI.

Getting Ready: Beta Program

The monitoring upgrade is almost finished, and a Beta program will open soon.

At that point, interested users can join by emailing the product manager. Feedback gathered during the preview drives the last tweaks before release.

Beta access unveils the Flow tab that displays jobs, dependencies, and status styles in one view. Selecting a job reveals the updated Job Definition screen, which switches between JIL text and a tabular layout that lists attributes such as envvars.

The Job Summary page now includes an Alarms tab, and the Runs table adds a Has Help Desk Ticket column that marks runs that have an associated ticket

Because v24.1 enables the new Monitoring capability by default, the interface activates immediately on fresh installs and upgrades. This default setting lets teams evaluate the overhaul without extra configuration.

Conclusion

AutoSys v24.1 switches Monitoring from opt-in to standard, so every install launches with the new interface ready. The Flow tab shows the flow for a selected View, while the Job Definition table converts detailed JIL data into quick-scan rows.

Operators view alarms and a “Has Help Desk Ticket” column with ticket numbers in Run details next to each run, and personal settings return at every login. Advanced Send Event options can schedule changes for a future date and time.

Together, these updates place key actions in one pane, simplifying oversight exactly as demonstrated in the latest preview.

RMT provides upgrade planning, operator training, and managed monitoring to embed v24.1 smoothly. Request a consultation to reserve a spot today.

In this article:
AutoSys v24.1 activates Monitoring by default and adds a Flow tab that visualizes job status and dependencies, tabular definitions, per-job alarms, and help-desk tickets, bringing faster triage and single-pane control.
Share on social media:
LinkedIn