Chase not seeing jobs that have completed

Products

• Workload Automation Agent

Issue/Introduction

The problem occurs when a job starts, runs, and completes on an agent, but the completion status update to the manager is delayed because all transmitter threads on the agent are busy.

If the chase utility is run during this specific window:

• chase requests the job status from the agent.

• The agent sees the job is finished and reports it is not running.

• This timing conflict results in a chase alarm being triggered, often followed immediately by a SUCCESS status, causing confusion.

Resolution

To resolve this, you must increase the number of threads available for outgoing communication on the agent to ensure statuses are sent back to the manager more efficiently.

1. Open the agentparm.txt file on the affected agent.

2. Add or modify the following parameter:

   communication.transmitter.pool.size=10

3. Restart the agent to apply the changes.