GRC User Hierarchy: sn_grc_user_hierarchy table not populatingIssue The sn_grc_hierarchy and sn_grc_user_hierarchy tables may fail being populated by the related scripts.CauseThere is a circular dependency that may break the user hierarchy, for which the table sn_gr_user_hierarchy will fail to get populated with data. The main recommendation is to not have a manager such as a CEO as the user at the top of the hierarchy, as that user will not report to any other user above. Also, should the user report to anyone, this should not be the same person or any previous managers from the manager hierarchy downstream.ResolutionThe prerequisites for the user roles and system properties are described in User hierarchy access control for issue and remediation task records. The way to find out the circular dependency in the instance of a small company is the following: Open the "Assigned to" user record, and from there check all the managers keeping track of their stored names in the sys_user table.At some point, a name will repeat and from there the loop starts. If you are able to reach to a user which has no manager, there is no loop, otherwise names will repeat. When the user hierarchy is huge and complex for a big organization, once the circular dependency manager is located, the administrator needs first to fix the data by removing the circular reference (manager field) of the top user record in the sys_user table.Only after the data fix the record can be populated in the sn_gr_user_hierarchy table via a user hierarchy schedule job.