Hi All,
We are currently using the Rapid Leaver configuration for termination processing, which is based on rule-driven application deprovisioning.
For example, we have five applications configured in the Rapid Leaver process: App1, App2, App3, App4, and App5. When a termination record is received from the authoritative source, the system initiates deprovisioning across all configured applications.
In a scenario where App3 encounters a workflow or code-related failure, we have observed that the termination process stops, preventing App4 and App5 from being processed.
Has anyone faced a similar situation? What is the recommended approach to ensure that a failure in one application does not block the deprovisioning of the remaining applications? Is there a way to continue processing the other applications while logging or handling the failed application separately?
Any guidance or best practices would be greatly appreciated.
@bhoyars_1 Could you please specify what code or workflow level failure you are referring to? If it is an unhandled exception comes during workflow execution, it’ll halt there itself. if you have handled every thing in beanshell, using a custom code, then you can handle them using try-catch block and exit gracefully or move to next app.
Hell Santhosh. Adding to Neel’s point, I would first identify where App3 fails: while the custom leaver logic is building or customizing the request, or later during provisioning.
IdentityIQ compiles the provisioning plan and partitions it into smaller plans, one per target. So if App4 and App5 are never attempted, I would look closely for an exception escaping from the custom rule or workflow before the complete plan reaches provisioning.
If your custom code processes applications individually, catch the exception at the application boundary, log App3, and continue instead of rethrowing it. I would not introduce a separate application loop unless your current customization already works that way.
For troubleshooting, temporarily set Provisioning Transaction Log Settings > Maximum Log Level to Success, reproduce the issue, and check Administrator Console > Provisioning (docs).
If App4 and App5 have transactions, they reached the provisioning layer. If they do not, check the leaver rule or workflow logs for an exception around App3.
For provisioning-layer failures, use the Provisioning Transactions details. For earlier custom-code failures, make sure the rule or workflow logs the application name and exception before continuing.