Loading

Sales Territories Territory Model Operations (Archive, Delete, Clone): Delays, Failures, and Monitoring

Date de publication: May 11, 2026
Description

Territory model operations in Enterprise Territory Management — including archiving, deleting, and cloning models — are asynchronous background jobs that can take several hours to several days to complete. During and after these operations, you may observe long delays, stuck status indicators, or related errors. This article explains why these delays occur and how to monitor and troubleshoot them.

 

Operations Are Asynchronous With No SLA

All territory model operations (archive, delete, clone) trigger multiple backend processes: clearing territory fields on opportunities, deleting shares and sharing groups, removing forecasting shares, and recalculating rules. These operations are queued as background jobs and run in batch. There is no service level agreement (SLA) or guaranteed completion time, and the duration scales with the volume of accounts, opportunities, and materialized shares associated with the model.

 

SHARE_DELETE_SERVICE Runs Only During Off-Peak Hours

Deletion of obsolete shares is handled by the SHARE_DELETE_SERVICE job, which runs only during peak or after-hours windows and processes shares when resources allow. For large territory models with millions of shares, this job can run for several days before completion. This behavior is by design and cannot be accelerated by Support.

 

Cloning Fails When Assignment Rules Contain Relative Date Filters

Territory model cloning fails if the model’s assignment rules contain relative date values such as “LAST 2 MONTHS” or “NEXT QUARTER.” Salesforce does not support relative date filters in territory assignment rules for cloning operations.

 

Archived Territories Remain Visible in Views by Design

When a territory model is archived, its territories remain visible in picklists and object views for users with the View All Records permission. This is by design. The only way to remove archived territories from views is to delete the archived model entirely.

Résolution
Step 1: Monitor progress in Background Jobs

Go to Setup > Background Jobs. Filter or search for “Territory Model Activation Chunk Job” or similar territory-related jobs to see the percentage completed and current status. This is the only in-product view of operation progress.

Running model operations during off-peak hours (nights and weekends) can reduce processing time because more infrastructure resources are available to the background jobs.
 
Step 2: For a cloning failure — remove relative date filters before cloning
  1. Go to Setup > Territory Models > [Your Model] > Rules.
  2. Edit any assignment rules that contain relative date criteria (e.g., “LAST 2 MONTHS,” “NEXT QUARTER”) and remove those date filters.
  3. Save the rules.
  4. Clone the model. Cloning should now succeed.
  5. After cloning completes successfully, re-add the date filters to the cloned model’s rules.
A cloning operation that is in progress cannot be canceled. If a clone is stuck, it must complete or fail naturally before the model can be deleted. Cloning operations that run for extended periods (more than 24–48 hours) without completion may have failed internally and will eventually transition to a deletable state.
 
Step 3: For a deletion delay — allow time and avoid off-hours bottlenecks

Territory model deletion involving large volumes of account assignments and shares can take several days due to the SHARE_DELETE_SERVICE job schedule. There is no method to expedite or force completion from the support side. Monitor progress in Background Jobs and allow the process to complete naturally. If the deletion is still in progress after 5+ business days, log a support case and reference the territory model ID for investigation.

 

Step 4: For archived territories appearing in views

Archived territories appearing in views is expected behavior. To remove them, the archived territory model must be deleted entirely (this also deletes all territory associations and account assignments in that model). If the archived model is still needed for reference, the territories will remain visible. Consider logging an Idea Exchange request for a filter to hide archived territories while retaining model data.

Ressources supplémentaires

How long should a territory model deletion normally take?

For small models (hundreds of territories, thousands of accounts), deletion typically completes within a few hours. For large models (tens of thousands of territories, millions of account assignments and shares), deletion can take several days due to the SHARE_DELETE_SERVICE job’s batch processing schedule. There is no SLA for territory model deletion.

My territory model shows “Archiving” status but has not changed for two days. Is it stuck?

An archiving operation in “Archiving” status for multiple days is likely delayed (not stuck) due to the SHARE_DELETE_SERVICE job processing schedule. Check Background Jobs in Setup for a “Territory Model Activation Chunk Job” entry showing percentage completion. If no job entry is visible and the status has not changed after 5 business days, open a support case.

Deleting previously archived territory models does not seem to speed up future archive jobs. Is that expected?

Yes. Deleting previously archived models removes their associated shares from the system, but this does not directly affect the processing time of future archive or delete operations for other models.

 

Archive a Territory Model

Clone Territory Models

Enable Sales Territories (000396697)

Numéro d’article de la base de connaissances

005036829

 
Chargement
Salesforce Help | Article