Jobs stay in RED RUNNING status after Database or Environment Outage

Products

• Automic Applications Manager

Issue/Introduction

Following a database issue or environment-wide interruption in CA Automic Applications Manager (AM), restarted jobs or jobs active during the outage show a status of RUNNING but the status color is RED instead of the standard GREEN.

• This typically occurs for jobs that were running prior to the interruption or restarted after the interruption.
• New jobs submitted after the environment is restored appear with the correct GREEN status.
• The job may appear stuck and fail to progress to a FINISHED status.

Environment

Applications Manager version 9.x and above

Cause

The RED status indicates that the Applications Manager Master has lost track of the operating system-level Process ID (PID) for the job.

Resolution

1. Verify OS Activity: Check the Agent server at the OS level (using ps -ef on UNIX/Linux or Task Manager on Windows) to see if the process associated with the job is actually running.
2. Allow Completion: If the process is still active and processing data, you may allow it to finish. Once the process ends, the Master should eventually update the status, or you may need to manually sync it.
3. Manual Intervention: If the job is confirmed stuck or the PID no longer exists:
   • Right-click the job in the Java Client.
   • Select Kill to terminate the tracking.
   • Rerun the job to initiate a new PID with a standard GREEN status.