Jobs or events stop running after user is removed from Admin group - Automic Automation

Products

• Automic SaaS
• Automic Automation

Issue/Introduction

Jobs, events, or schedules in Automic Automation stop executing immediately or after a short delay. This behavior occurs after a user account, which was previously used to start these objects, is removed from the Admin user group or has its privileges revoked or changed.

This may show up as:

• Active events or schedules stop processing new executions.
• Jobs associated with specific schedules stay in a "Waiting" or "Blocked" status.
• The issue coincides with the removal of a specific user from an admin group.

Environment

• Automic Automation - all versions

Cause

In Automic Automation, the execution of events and schedules is tied to the security context of the user who started the object. If that user loses the necessary privileges (such as membership in the Admin group), the system can no longer authorize the execution of the tasks under that user's identity.

Resolution

Perform the following steps to restore job execution:

1. Identify the user who originally started the impacted Event or Schedule object.
2. If immediate restoration is required, temporarily add the user back to the Admin group.
3. To resolve the issue permanently, log in with a current authorized administrator account.
4. Stop the affected Events and Schedules.
5. Restart the objects using the current administrator account to ensure they run under a valid security context.

There is currently a request for enhancement (RFE) for this topic.  To express interest in the same, follow the steps in the Enhancement request process for Broadcom's AOD Division article.  Reference this article (id 452559) when doing so.