AutoSys Global Variables — Stale Flags That Skip Batch Runs

AutoSys global variables live in the Event Server. Any job can read them. Any job can write them. They persist until explicitly changed.

That last sentence is where teams get burned.

A flag set to 'COMPLETE' on Monday is still 'COMPLETE' on Tuesday. A counter that reached 5000 yesterday is still 5000 today unless you reset it. This article covers the patterns that work — and the one stale-value trap that breaks workflows silently.

Setting a global variable from a job

Jobs set global variables using the sendevent command with the SET_GLOBAL event. This can be done from within the job's script or from the command line.

The syntax is: sendevent -E SET_GLOBAL -G "VARNAME=value". No spaces around the equals sign.

Critical: SET_GLOBAL events are processed asynchronously. There's a small delay (typically <1 second) between the command and the value being readable by other jobs. If your downstream job starts immediately after setting a variable, it might not see the value yet. Use condition dependencies to enforce order if timing matters.

#!/bin/bash
# Script that processes records and sets the count as a global variable

RECORD_COUNT=$(wc -l < /data/processed_trades.csv)

# Set the global variable in AutoSys
sendevent -E SET_GLOBAL -G "TRADE_COUNT=${RECORD_COUNT}"

# For workflows with date-stamped globals (recommended for daily runs)
DATE=$(date +%Y%m%d)
sendevent -E SET_GLOBAL -G "TRADE_COUNT_${DATE}=${RECORD_COUNT}"

echo "Processed ${RECORD_COUNT} trades, set TRADE_COUNT global variable"
exit 0

Reading a global variable in a JIL condition

You can reference global variables in JIL conditions using the variable() function. This lets you create data-driven conditions.

Syntax: condition: success(job_a) AND variable(TRADE_COUNT) >= 1000 The comparison operators work: =, !=, <, >, <=, >=. String comparison works too: variable(STATUS) = 'COMPLETE'

Critical: variable() returns an empty string if the global doesn't exist. In numerical comparisons, empty string compares as 0. That can cause false positives — a missing variable might silently pass a >=1 check.

/* Read a global variable in a condition */
insert_job: validate_trade_count
job_type: CMD
command: "/scripts/validate_count.sh ${TRADE_COUNT}"
machine: server01
owner: batch
condition: success(process_trades) AND variable(TRADE_COUNT) >= 1

/* String comparison with global */
insert_job: check_status
job_type: CMD
condition: variable(WORKFLOW_STATUS) = 'READY'

/* Dangerous: missing global passes >= 0 check */
/* If TRADE_COUNT never set, this condition is TRUE */
condition: variable(TRADE_COUNT) >= 0

/* Safer: check existence and value */
condition: variable(TRADE_COUNT) != '' AND variable(TRADE_COUNT) >= 100

/* Set a global variable via sendevent from command line */
# sendevent -E SET_GLOBAL -G "PROCESS_DATE=20260319"

/* Check current value of a global variable */
# autostatus -G TRADE_COUNT

Global variable naming, lifecycle, and best practices

Global variables persist in the Event Server until explicitly changed or cleared. They do not reset between daily runs — a value set yesterday is still there today unless something overwrites it. This is both powerful and dangerous.

Lifecycle: Created on first SET_GLOBAL. Persists indefinitely. Cleared by SET_GLOBAL with empty value (or by database cleanup). Survives Event Processor restarts, failovers, and system reboots.

Best practices that separate senior engineers from beginners: 1. Always use a naming convention with a workflow prefix (e.g., TRADING_RECORD_COUNT not just COUNT) 2. Reset flags and counters at the start of each workflow run, not the end 3. For per-run state, include the date in the variable name (e.g., TRADING_COUNT_20260319) 4. Document every global variable your workflow uses — undocumented globals become tribal knowledge 5. Audit global variables monthly with autostatus -G % to catch stale or orphaned ones 6. Never assume a global exists. Check before reading.

# PATTERN: Reset globals at the START of a workflow (not end)
# Add this as the first job in your box:

insert_job: PRD_TRADING_RESET_GLOBALS
job_type: CMD
box_name: PRD_TRADING_EOD_BOX
command: /scripts/reset_trading_globals.sh
machine: server01
owner: batch
# No condition — first job in box

# reset_trading_globals.sh contents:
# sendevent -E SET_GLOBAL -G "TRADING_RECORD_COUNT=0"
# sendevent -E SET_GLOBAL -G "TRADING_STATUS_FLAG="
# sendevent -E SET_GLOBAL -G "TRADING_PROCESS_DATE=$(date +%Y%m%d)"

# PATTERN: Date-stamped globals for per-run state
DATE=$(date +%Y%m%d)
sendevent -E SET_GLOBAL -G "TRADING_COUNT_${DATE}=5432"
# Downstream job reads: variable(TRADING_COUNT_20260319)

# List all current global variables
autostatus -G %

# Clear a stale global
sendevent -E SET_GLOBAL -G "STALE_FLAG="