Job stuck in Starting state

Products

• Autosys Workload Automation

Issue/Introduction

Job got triggered and got stuck in Starting state. Due to this Chase alert generated.

Environment

Agent R12.1 Linux

Cause

Job has a Profile attribute defined. When job triggered, it is taking time in sourcing the profile file 

Resolution

In this case there is a custom script in the profile file which connects to a remote database and it is taking time due to network issue. Once it got fixed the job started running as expected.