AsyncApexExecutions Limit exceeded

On This Page


When you see this error, it often occurs repeatedly and quite frequently. This indicates that too many asynchronous apex jobs have executed in the last 24 hours. The limit operates on a rolling 24-hour basis, so you won’t see any sort of “reset” at midnight for instance, and may well see the error continue through all hours when it does happen. 

Kubaru uses several recurring asynchronous jobs so that we can keep up on data as close to real-time as possible, so that assignments go out as quickly as possible among other functions. This means that by design we have several jobs that execute throughout each day. In addition, you may have other local customizations and/or other managed packages that also drive up your asynchronous usage. 


It is suggested that you first identify the jobs that have the highest consumption toward this limit. You can do this by monitoring your apex jobs. Once identified, the exact solution will vary depending on the biggest offenders, but the goal will be to tamper usage in whatever way you can. You can reach out to us at for assistance with this.

If you find that Kubaru is on the list of offenders, there’s a way (as of Version 4.9) to add time between each job cycle, thus reducing the number of total jobs. Though it also will increase the time it takes to make assignments, so we suggest being judicious about its use. 

  1. At the top-right of the page, click your name if you are in Salesforce classic, or the gear if you are in Lightning experience, then select Developer Console
  2. In the window that pops up, go Debug > Open Execute Anonymous Window, or press Ctrl+E as a shortcut. 
  3. In the new popup (labeled Enter Apex Code), enter nwcs_ldl.LD_Leads.UpdateGlobalSettings(new Map<String,Object>{‘nwcs_ldl__BatchChainDelay__c’ => 1}); and click the Execute button at the bottom-right. This will add one minute between each job cycle. The value is found after the “=>” in the statement. To remove the delay, you can replace this with null. You can also replace with 2, 3, etc. to increase the delay. 
Was this article helpful?

On This Page