Apex CPU Time Limit Exceeded

 

What is a CPU timeout error?

Salesforce limits CPU usage to 10 seconds for synchronous transactions and 60 seconds for asynchronous transactions. Seeing the error “Apex CPU time limit exceeded” means your transaction is taking too long and can’t be completed. It’s also likely a signal of greater problems in your system. It’s common to see this error when you’re inserting or updating records in Salesforce, particularly when tools, integrations, and automation are putting a strain on your system.

What’s Slowing Your System Down?

Unless you have a clear idea of what’s causing your CPU timeout error, you’ll need to conduct an audit to find its source. , rather than systematically examining everything that’s going on in your system, it’s best to start where the problem is most likely to occur: on the creation of a lead, contact, or account.

Next, narrow your investigation to the types of actions that tend to create CPU timeout errors: database queries, process builders/workflow rules, and Apex code. By determining how long it’s taking your system to run each of these functions, you’ll then be able to identify which one is slowing it down.

Optimizing to Avoid CPU Timeout Errors

There are two primary situations in which a CPU timeout will occur. The first is that your processes are simple, but you’re processing too many records at once. In this case, the record count alone will force your code to hit the processing limit. To avoid this, process your manual inserts in smaller batches, schedule your automation to run only when and where you need it to, and control batch size in automated updates.

The more complicated scenario occurs when you’re processing a smaller number of records but the update is too complex for the system to handle within the CPU time limit. Below are examples of this issue, and how to avoid it.

Validation Rules

Truthfully, it’s uncommon for validation rules to cause “Apex CPU time limit exceeded” errors. But it can happen. When it does, it’s likely due to one of two reasons: either you have too many validation rules on a single object, or you have an excessive number of statements in a single validation rule. Eliminate these issues and your validation rules will run error free.

Process Builders

By far the most common reason that process builder causes CPU timeout errors is having multiple process builders on one object. It’s a best practice for process builders to have only one per Salesforce object. Alternatively, CPU timeout errors can happen when process builders are not firing on selective events, which can create a volume issue unnecessarily.

In either situation, consider migrating your automation from process builder to to an Apex trigger. Triggers can work much faster and will be less likely to cause an error.

Flows

If you’re using flows that happen after save instead of using the new before save flow feature you may run into a CPU timeout error. If you want your flows to fire before insert, you’ll need to migrate existing flows to this new model and select the “before save” option upon creation of your flow.

Apex Code

There are many situations in which Apex causes an “Apex CPU time limit exceeded” error. Here are the most common scenarios.

• A circular update between two objects. This will cause a never-ending execution of Apex and a CPU timeout.

• Too much processing in a before trigger. Try moving processing to an after trigger.

• Too many nested loops. Loops more than two layers deep can sharply increase CPU time. Try using more code blocks instead of doing too much in a single set of nested loops.

• Recursion. Having an update call the same update trigger more than once within one transaction can cause problems.

• Querying and updating the same object many times. Instead, do one update on one object.

• Too many triggers. Limit how many triggers you’re firing on one update.

• Architecture issues. Multiple fields being tracked on an object like timestamps to track when different fields are updated could be all moved to a related object instead so that the related object is modified, offloading processing on an object that might already have a lot happening to it

Call a method of one class in another class : APEX : Salesforce

 You can use two approaches:

1.Use Static methods

You cannot use controller2 instance methods here

public class controller2 
{
    public static string method2(string parameter1, string parameter2) {
        // put your static code in here            
        return parameter1+parameter2;
    }
    ...
}

In a separate class file call method2()

// this is your page controller
public class controller1
{
    ...
    public void method1() {
        string returnValue = controller2.method2('Hi ','there');
    }
}

2.Create an instance of the other class

public class controller2 
{
    private int count;
    public controller2(integer c) 
    {
        count = c;
    }

    public string method2(string parameter1, string parameter2) {
        // put your static code in here            
        return parameter1+parameter2+count;
    }
    ...
}

public class controller1
{
    ...
    public void method1() 
    {
        controller2 con2 = new controller2(0);
        string returnValue = con2.method2('Hi ','there');
    }
}

If your methods are in a package with a namespace

string returnValue = mynamespace.controller2.method2();

--------------------------------------------------------------

public class ClassA {

    public list<Account> method1(){
        
        List<Account> lstacc = [SELECT Id,Name from Account];
    	return lstacc;
    }

}

////////////////////////////////////////////////////////////////

public class ClassB {
	
    ClassA ca = new ClassA();
    List<Account> acc = ca.method1();
    
    public static list<Contact> method2(List<Account> accountList){
        
        List<Contact> lstcon = [SELECT Id,LastName from Contact WHERE accountId IN: accountList];
        SYstem.debug('List of contact--->'+ lstcon);
        return lstcon;
    }
}

Events/Tasks : Open Activities/Activity History

 There are actually four relationships for activities: 

Tasks, 

Events, 

OpenActivites

ActivityHistories. 

The two real objects are Tasks and Events

OpenActivities show open tasks and events today or in the future.

ActivityHistories shows closed tasks and events before today (in the past). 

When you want to show the history or future activity of a record, you use the two "hybrid" objects

When you want to create a real task or event, you use the two real objects (They'll automatically appear in the appropriate hybrid relationship).