Activating, Archiving, Deleting, Cloning a territory model is taking a long time to complete

This article explains why activating, archiving, deleting, or cloning a territory model can take a long time to complete or appear stuck, and what to keep in mind when planning these operations.

Why This Happens

Activating, Archiving, Deleting, and Cloning a territory model are all asynchronous jobs that do not have a defined SLA to complete. They are also subject to dequeue latency. It is important to plan these types of activities with a potential delay in mind. Dequeue latency is known to happen especially around release time, as certain jobs like search indexing could take most of the resources.