A Remote Agent can appear stuck in a RUNNING status even though the Agent processes have stopped and the entry in the database also shows a stopped status.
CA Automic Applications Manager
Version: 9.3x, 9.4x
This usually occurs after a cloning a database or if a Server is abruptly shutdown without stopping an Agent. The database entry can be stuck in an incorrect status and sometimes needs to be manually updated. Agents improperly migrated or server is abruptly shutdown without stopping an Agent.