Large hierarchies are hierarchies with more nodes than the maximum trigger hierarchy limit. Hierarchy processes for large hierarchies would encounter Salesforce governor limits if

Customer 360 for Salesforce

processed hierarchy changes synchronously. To avoid these limits,

Customer 360 for Salesforce

uses asynchronous batch jobs to process changes to large hierarchies.

The following batch jobs process hierarchy changes asynchronously:

Asynchronous Hierarchy Process

Processes add, move, and remove operations for large hierarchies.

Asynchronous Cloning Process

Processes clone operations if the number of nodes to clone is larger than the maximum trigger hierarchy limit.

If you abort an asynchronous hierarchy batch job, you could get unexpected hierarchy results. Do not abort a hierarchy batch job.

When you delete a leaf node from a large hierarchy,

Customer 360 for Salesforce

processes the delete synchronously.

Customer 360 for Salesforce

processes all other changes to large hierarchies asynchronously.