Chase Alarm

[Corrie Kantowski]

Almost every day since 7/29, a specific job is recording a chase alarm during it's run. The job ends up with a status of SUCCESS, but I would like to know more about this alarm. 

STARTING    CHANGE_STATUS        Aug 8, 2024 3:57:55 AM    (PD) Processed    Aug 8, 2024 3:57:56 AM
RUNNING    CHANGE_STATUS    <Executing at WA_AUTOSYS>    Aug 8, 2024 3:58:07 AM    (PD) Processed    Aug 8, 2024 3:58:08 AM
CHASE    ALARM    <ERROR: Job in RUNNING state, but the user process is not running on machine: autosys-prd.acsu.buffalo.edu_AUTOSYS>    Aug 8, 2024 3:59:10 AM    (PD) Processed    Aug 8, 2024 3:59:11 AM
FAILURE    CHANGE_STATUS    <Job is not RUNNING. chase sending a FAILURE event.>    Aug 8, 2024 3:59:10 AM    (PD) Processed    Aug 8, 2024 3:59:11 AM
SUCCESS    CHANGE_STATUS        Aug 8, 2024 4:00:00 AM    (PD) Processed    Aug 8, 2024 4:00:01 AM
    CHK_TERM_RUNTIME        Aug 8, 2024 3:58:07 AM    (PD) Processed    Aug 8, 2024 4:00:00 AM

[Richard Heaney]

Hi Carrie,

There is some good information about CHASE in this link:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/reference/ae-commands/maintain-system/chase-command-verify-job-starting-or-running-status.html

I don't know how your job is set up but it could be something similar to having a load balancer on the agent machine and it might be looking at the incorrect node. Or maybe the CHASE timing is too short and in that case it might need to be increased.

Thanks

Richie