"Perform Identity Request Maintenance" is stuck

Which IIQ version are you inquiring about?

Version 8.3

Please share any other relevant files that may be required (for example, logs).

Share all details related to your problem, including any error messages you may have received.

The “Perform Identity Request Maintenance” is stuck and in pending state for last couple of days, even though we delete the task from debug and re run same thing happening the task is in pending state and stuck at some thread.

Due to this all the Access Requests are in “Provisioning” state even though all the request are Committed.

Please find the below Post which might solve your issue here: Perform Identity Request Maintenance task does not complete Pending requests - IdentityIQ (IIQ) / IIQ Discussion and Questions - SailPoint Developer Community Forum

If the above post doesn’t help, it would really be helpful if you can share the Task config and if they are multithreaded.
Additionally, have you modified the OOTB workflows for provisioning within your environment? If yes I would suggest to use the OOTB workflows and only reference them once your modifications are made in your plans.

I would suggest the following running a cleanup operation for the access requests that were processed from the day you have encountered this issue.


below is out OOTB TASK - please suggest if you have any inputs

Perform Identity Request Maintenance.xml (1.1 KB)

@sunilasm , how are you?^

Hos is the configuration? how many days are you looking for? Have you enabled partition?
Is the identity request being deleted by a separated process?
Share the configuration of the task not the XML, take a screenshot

Hi @ipobeidi - i am attaching the OOTB task xml.

We also enabled the trace and i am attaching the log here, please kindly provide if you have any advice.
Perform Identity Request Maintenance.xml (1.2 KB)
Log_0412.txt (69.3 KB)

When any task gets stuck I always start with looking at stack traces in debug. If it’s partitioned it could be multiple ones, on different servers. Try to identify the threads for your task and provide stack trace(s). That way we can see at what point it’s stuck.