search cancel

Long delay between the STARTING and RUNNING status for a job


Article ID: 239576


Updated On:


CA Workload Automation AE


A long delay is observed between when a job goes to STARTING status and when the job actually executes on the agent and goes to RUNNING status.


Release : 12.0

Component : CA Workload Automation AE (AutoSys)


This behavior can be caused when the job profile and/or the /etc/auto.profile have an issue that causes them to take a long time to source. To test for this condition, logon to the agent machine and source the file specified as the job profile along with /etc/auto.profile. If there is any delay observed when manually sourcing those files on the agent machine, that delay would also be present when the agent sources them while running the job. The job will not execute and be placed into RUNNING status until these profiles are sourced.