After a process hierarchies job completes, you can view the job metrics on the My Jobs page. You can view metrics such as the number of relationships processed, the number of records indexed, and the number of records processed for the inheritance of dynamic field definitions.
When a job is running and a second job is triggered for the same hierarchy, the status of the second job changes to Queued. If a third job is triggered for the same hierarchy while the second job is queued for processing, the job status changes to Skipped. When the queued job runs, it indexes all the records that the hierarchy contains, and the skipped job becomes redundant and doesn't run.
A process hierarchies job includes steps to index records and inherit dynamic field definitions within a hierarchy.
The job might fail in the following reasons:
•The number of hierarchies that are created based on a hierarchy model exceeds 250,000.
•The records of business entities that are part of a hierarchy model require reindexing.
•The number of hierarchical relationships in all the hierarchies of a hierarchy model exceeds 25 million.
•The hierarchy model is disabled for search after the job was run.