2

If a certified managed package initiates batch apex, does it come under governor limits of native org for batch apex?

e.g. per documentation:

The maximum number of asynchronous Apex method executions (batch Apex, future methods, Queueable Apex, and scheduled Apex) per a 24-hour period = 250,000 or the number of user licenses in your organization multiplied by 200, whichever is greater

Does this include batch apex initiated by a managed package? Or does managed packages get a separate limit for batch apex?

I know from the documentation that managed package has separate number of DML and SOQL execution limit per transaction.

Apex Limits

I was wondering what the behavior is for batch apex.

3

As per the link in your question, the following are not separate limits for the managed package, rather they're counted towards the whole org:

  • The total heap size
  • The maximum CPU time
  • The maximum transaction execution time

Having said that, your DMLs inside the batch will have a separate limit for the managed package namespace, though the maximum CPU time for an example will stay the same for all apex in your org, regardless whether the code is executed withing the namespace of the managed package or your org in general.

So in regards to method executions, this link says that the maximum number of asynchronous Apex method executions falls into the Force.com Platform Apex Limits

"The limits in this table aren’t specific to an Apex transaction and are enforced by the Force.com platform."

Meaning that the governor limit will apply for the managed package as well.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.