Persistent Inactive Status for Scheduled Jobs in JSCH Objects

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When you change a job status from active to inactive within a scheduled JSCH object in Process Monitoring, the inactive status persists across daily reloads instead of reverting to the Process Assembly design configuration․​‌‍ This behavior affects both versions 12․3․5 and 24․4․x․ 

ERROR MESSAGE (if applicable): None reported․

SYMPTOMS:

• A job is deactivated in Process Monitoring for a single day․

• The JSCH object reloads at 00:00 the next day․

• The job remains inactive on subsequent days despite being active in Process Assembly․

CONTEXT: Occurs during daily schedule generation when active instances are modified directly in Process Monitoring․

 

Environment

CA Automic Workload Automation - Automation Engine

 

Cause

Modifications made directly to an active JSCH object instance within Process Monitoring are preserved across daily generation and reload boundaries․ The daily reload does not overwrite modified runtime instances with the base template from Process Assembly․ See Modifying Active Schedules

 

Resolution

Prerequisites:

• Access to Process Monitoring

• Permissions to modify active JSCH objects

 

STEPS:

1․ Deactivate the Job For the Target Night

Path: Process Monitoring -> Active JSCH Object

Action: Locate the target job within the scheduled JSCH object and uncheck its Active flag․

EXPECTED: The job will not execute during its scheduled time that night․

 

2․ Reactivate the Job for the Following Day

Path: Process Monitoring -> Active JSCH Object

Action: At any time before the next day's scheduled execution time, return to the active JSCH object in Process Monitoring and check the Active flag back on․

EXPECTED: The job status updates to active immediately and executes normally at its scheduled time without requiring an object reload or system cycle․

NOTE: Because modifications in Process Monitoring create a persistent state change on the active instance, the job remains inactive until manually reactivated ․ You do not need to perform this change in a tight window between execution and midnight; you can safely reactivate it the following day as long as it is done prior to that evening's runtime (e․g․, reactivating at 3 PM for an 11 PM run).

 

VERIFY SUCCESS:

• Check the active JSCH object after midnight to confirm the job status is active․

• Monitor the execution at the scheduled time to ensure the job runs successfully․