Enterprise Territory Management (ETM) rules on Account are run automatically when creation of an Account. However, they do not run automatically on account update. Out of the box, here are some options available.

Include the checkbox on the layout

                                

Run the ETM rules from settings, setup -> territory models -> pick a territory and run all rules assigned to the territory

  

 

Here are some limitations with running ETM rules automatically

• ETM rules do not run on inline edit
• DML updates from Apex do not run ETM rules

To programmatically run ETM rules on every account update, you could fire off a REST callout to update the account. This will run the ETM rules. Here is a sample code that uses Queueable job to perform this.

Make sure to pass the accountId and any other fields you would like to include in the dataWrapperJson variable.

 What is a Apex CPU timeout?

For every transaction like updating an account or creating a new contact, automation's that run in the background get 10 seconds. If your automation's take more than 10 seconds that leads to a Apex CPU timeout exception and the operations is aborted. Note that in most orgs you get an additional 5 seconds as a grace period, however generally you should strive to keep your automation's down at 10 seconds.

What causes CPU timeout?

It's not just apex code that causes a Apex CPU timeout exception. Flows, process builders and apex triggers equally contribute towards this exception. Bad design and implementation of these automation's lead to this exception.

Where do i start?

Event Monitoring

How to Debug ?

 

How to reduce CPU time?