The Run Loading Procedures step in the nightly RiskFabric Processing job runs longer than historical run times, or appears to be hung and does not complete after several days.
Release : 6.x
Component : RiskFabric Processing
The Run Loading Procedures job step creates indexes on certain core RiskFabric database tables. Resource locks on these indexes by other processes, including those initiated by other SQL Server Agent jobs, will prevent the job from proceeding until the locks have been released.
If a custom maintenance job is attempting to place a lock on an index that is currently locked by an Information Centric Analytics (ICA) procedure at the same time ICA's procedure is attempting to place a lock on an index that is currently locked by a custom procedure, this will create a deadlock condition that causes both jobs to hang.
Schedule third-party index maintenance jobs to run and complete outside the hours in which the RiskFabric Processing job runs.
Refer to Microsoft's documentation for assistance with identifying resource locks: