You can trace the following methods to troubleshoot issues with Identity Auditor:
com.sun.idm.auditor.policy to trace issues with Audit Scans.
com.sun.idm.auditor.accessreview to trace issues with Access Reviews.
com.sun.idm.auditor.report to trace issues with Audit Reports.
com.sun.idm.auditor.view to trace issues with Auditor Views.
In addition, you can set the following hidden flags by modifying Forms or TaskDefinitions:
Audit Policy Scan Task - maxThreads (int). Number of concurrent threads used. (Defaults to 5).
Audit Policy Scan Task - userLock (int). Time (in milliseconds) to wait to acquire a lock on the User object. (Defaults to 5000)
Audit Policy Scan Task - scanDelay (int). Time (in milliseconds) to delay between launching a new scan thread. (Defaults to 0, no delay)
Audit Policy Scan Task - clearuserLocks (boolean). If true, the scanner attempts to clear the user lock before scanning.
In addition, the Show Timings page (/debug/callTimer.jsp) provides the following information:
How long it takes to fetch the initial User view, with no resources, during the scan
How long it takes to refresh the User view, including resources, during the scan
How long it takes to evaluate the policy on the User view
How long each user scan takes, including User view fetch, policy evaluation, and so forth
How long it takes to fetch a list of users for access review
How long it takes to evaluate the attestation rule in access review