When an Identity Governance ETL job remains in the 'create' state, it may prevent new ETL processes from executing. This article provides instructions to purge the stuck job and restore functionality.
The ETL workflow becomes stuck in a 'create' state due to an interrupted process or an error during execution. Because CA Identity Governance enforces a single-process execution limit for ETL tasks to prevent data corruption, a stuck job effectively locks the service. Without manual intervention to purge this process, the system is unable to initiate new ETL jobs.
To remove the stuck ETL workflow and permit new processes to run, the system configuration must be modified to allow the purging of ETL tasks:
etl to locate the relevant configuration settings.true:purge.etl.allowPurgeCompletedpurge.universe.purgeETLProcessespurge.etl.allowPurgeAll
Once the stuck workflow is removed, the system will allow the initiation of a new ETL process.
To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.