Activity Forums Salesforce® Discussions Query Exception

  • Gourav

    Member
    June 8, 2016 at 11:48 am

    Yes, that means it's taking too long. A couple ways to get more CPU time are to put the code in an @future method (you get 60 seconds of CPU instead of just 10 seconds), or implement it as a Batch Apex job. Since both of these methods are asynchronous, the trigger and associated DML will complete before the calls to the AccountServices methods are made - but they will be called eventually. Would this work for you? or Try to filter your query to reduce number of records.

Log In to reply.

Popular Salesforce Blogs

Popular Salesforce Videos