Avoid Workflow Disruptions by Enabling Elastic Limits for Batch Jobs (Beta)

The elastic limits beta feature is now available to Batch jobs in addition to future methods and Queueable jobs. Elastic limits helps prevent execution failures and limit exceptions when your org exceeds its standard rolling 24-hour asynchronous job limit. With this feature, you can continue to enqueue asynchronous jobs up to a higher elastic asynchronous job limit. If asynchronous jobs surpass the standard limit, the system throttles the processing rate of in-flight Batch jobs and limits new Batch jobs to 1 active job at a time.

Where: This feature is available to orgs where the "Use elastic limits for asynchronous Apex jobs (beta)" setting is enabled. This feature is available in Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

Important Elastic Limits for Asynchronous Apex Jobs is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer’s sole discretion.

How: In Apex Settings, turn on "Use elastic limits for asynchronous Apex jobs (beta)". To view the org’s elastic limit, hover over the tooltip next to the setting. To check asynchronous job usage, use methods from the OrgLimits class.

To test how asynchronous jobs perform in elastic processing conditions, set the Asynchronous Apex job limit override for nonproduction orgs. See Test Elastic Limits by Overriding the Asynchronous Apex Job Limit in Nonproduction Orgs.

Note A production org’s elastic limit equals its 24-hour rolling asynchronous Apex limit plus additional capacity. This additional capacity is now capped at either its licensed asynchronous Apex job limit or 2 million jobs, whichever is lower. Previously, this additional capacity was capped at 10 million jobs.