How to resolve a Job or Process Flow that is stuck in SELF WAIT status

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Why is one or more Jobs and/or Process Flows stuck in a SELF WAIT status?

Resolution

SELF WAIT expected behavior:

A Job or Process Flow may have the 'Single Run' option enabled as described in the doc link here.

When enabled, two instances of the Job cannot run concurrently. The second instance will show a status of SELF WAIT until the first completes.

If a task is stuck in SELF WAIT status, search the Backlog to see if another instance of the task is still exist in the Backlog. Depending on the status of the task, you may need to let it finish or take action against it, such as deleting it to drop the task into History.

What if there is no other instance of the task in the Backlog (unexpected behavior):

There a few options that can be taken to attempt to resolve SELF WAIT status.

• Search the Backlog to see if there is another instance of the task in the Backlog and take the necessary action to remove the task from the Backlog such as deleting the task, waiting for it to finish, etc.
  
  
• If not other instance of the task is found in the Backlog, stopping and starting the RMI thread, not the actual process, will force the RMI to re-evaluate the Backlog and this may clear the SELF WAIT Job and allow it to go into Queued and then Running. 
  
  The RMI thread can be stopped and started by right clicking the Master or Automation Engine from the 'Agent Summary' Window and selecting 'Stop'. Once stopped, right click again and selecting 'Start'
• If restarting the RMI thread does not resolve the issue (in most cases it should), restarting the Applications Manager RmiServer process or service (Windows OS) may help resolve the issue.
  
  On Unix/Linux, the RmiServer process can be stopped with a "stopso rmi" or "stopso all (this stops agentservice as well)" command. Once process have been stopped, restart process with 'sttartso rmi' or 'startso all' commands.
  On Windows, restart the watchworx service (AWW-<MASTERNAME>).