ESP jobs are not triggering from ESP proxy

Products

• ESP Workload Automation

Issue/Introduction

When a Trigger (TR) command is issued to the proxy, the audit log shows "Event triggered," but no application is created and event statistics are not updated.

 

Resolution

The review of the system dump shows that the proxies were in a QUIESCED state. 

 

Although the proxies are set to ROUTING MASTER by default and the system indicated that scheduling was active, changing the setting to ROUTING LOCAL revealed the actual QUIESCED status.

 

To resolve this, delete the old triggered events and restart the proxies.