[SalesForce] scheduled apex+Too many DML rows: 10001

I am getting this error when i look at my apex jobs UI

"Scheduler: failed to execute scheduled job: jobId: 7072000002391Am,
class: common.apex.async.AsyncApexJobObject, reason: Too many DML
rows: 10001"

All suggestions I have seen tell me to schedule the job but it scheduled to go everyday – do I need to break it in to smaller batches still?

This is the code, any suggestions are most appreciated

global void execute (SchedulableContext sc) {
    List<Contact> agentsToRemind = new list <Contact>
        ( [SELECT Id FROM Contact WHERE Days_since_web_registration__c  > 90 
          AND Luxury_Agent_ID__c = NULL AND join_heroes_reminder_sent__c= NULL ]);
    IF(agentsToRemind.size()>0){   
        update agentsToRemind;
    } 
}

Best Answer

You have hit a DML limit. While the algorithm you mention is correct:

if you created a class like this and scheduled it to run once a day it would update everyone in the loop, which would then be picked up by a workflow I have in there

You're not taking into account Salesforce limits. You're limited to manipulating only up to 10000 records in one execution context. If you have more than 10000 contacts in your org, you will get the exception you mention above. Read more about limits here: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm

In your case, the best way to overcome this limitation is to use your scheduled job to trigger a batch Apex job: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_batch_interface.htm

Related Solutions

[SalesForce] Too many DML rows: 10001 issue

Your unit tests should not be operating on data which exists in your production org.

If the receiving_Tests class is annotated with @seeAllData=true, switch it to false and then create all of the data that you need for the test within the test itself.

If the receiving_Tests class has an API version earlier than v24, you should modify it to v24 or later, make any other corrections to the tests so that it passes all tests and deploy it to production as well.

This looks to be a good opportunity for you to test your Large Data Volume performance by creating more than 10,000 records in the setup for your test and ensuring that the test is successfully executed in the sandbox.

Isolation of Test Data from Organization Data in Unit Tests

[SalesForce] Scheduled Apex Class – Too many DML rows: 10001

AJ,

This code should get you going. It allows you to schedule and batch....

global class updateMonthlyActivityCount Implements Schedulable,  Database.Batchable<sObject> {

    global void execute(SchedulableContext sc) {
        Database.executeBatch(this, 200); //You can change the "200" number for anything else
    }

    global Database.QueryLocator start(Database.BatchableContext BC) {
        string query = 'SELECT Id, Monthly_Activity_Count__c FROM Account WHERE Monthly_Activity_Count__c = null OR Monthly_Activity_Count__c > 0';

        return new Database.getQueryLocator(query);

    }

    global void execute(Database.BatchableContext BC, List<sObject> scope) {
        List<Account> accList = (List<Account) scope;

        for(Account a : accList){
            a.Monthly_Activity_Count__c = 0;
        }

        update accList;
    }

    global void finish(Database.BatchableContext BC) {

    }
}

Best Answer

Related Solutions

[SalesForce] Too many DML rows: 10001 issue

[SalesForce] Scheduled Apex Class – Too many DML rows: 10001

Related Topic