Cleanup Submitted Tasks or Explore Correlate tasks stops running after initiator user deletion
Article ID: 444818
Updated On:
Products
Issue/Introduction
Scheduled tasks, such as Cleanup Submitted Tasks or Explore and Correlate, stop executing for extended period of time.
Investigation reveals these tasks fail to trigger because the user who originally scheduled them is inactive or deleted from the system.
The User Console interface lacks an option to modify the initiator once the task is created, leading to orphaned jobs that no longer run.
Environment
Product: CA Identity Manager, CA Identity Suite
Version: 14.x, 15.x
Cause
Scheduled tasks in the system are tied to the security context of the initiator user. Unlike Bulk Task Definitions, the Cleanup Submitted Tasks and Explore Correlate tasks configurations do not allow changing the initiator to a service account after submission. When the initiator user is offboarded or deleted, the job becomes orphaned, resulting in silent failures
Resolution
Reschedule Task with Service Account: Recreate the Cleanup Submitted Tasks and Explore Correlate tasks in the User Console. Use a dedicated service account as the initiator to ensure task continuity regardless of individual administrative user status.
Consider running Cleanup submitted tasks from database level: Refer to Identity Manager: Task Persistence Database Cleanup Using Stored Procedures for scripts and Cleanup Submitted Tasks Tab for documentation.
Perform Database Backup: Ensure a full backup of the Task Persistence database exists before proceeding with manual cleanup.
Additional Information
This issue is targeted to be fixed in release 15.0.1. Subscribe to this article to receive updates on the fix status by following the steps in .
Feedback
