The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

How elastic limits extend Async Apex capacity and throttle processing in Winter '27 (opens in a new tab)

You will learn how the Winter '27 extension of elastic limits increases Async Apex capacity while throttling throughput, and how to monitor usage with the OrgLimits class.

The Winter โ€™27 release extends the beta capability of elastic limits to Batch jobs, following its initial introduction for Queueable and Future methods in Summer โ€™26. When standard asynchronous governor limits are reached, the system allows additional enqueues up to a secondary cap calculated as the minimum of two million or the standard limit. Enqueued jobs beyond the baseline trigger throttling, which slows active processing and restricts Batch jobs to a single concurrent instance.

Developers can track consumption using the OrgLimits class, specifically querying the DailyAsyncApexElasticExecutions metric alongside the standard daily limit. The feature remains exclusive to production environments, meaning sandbox and trial orgs do not receive the extra capacity. Salesforce intentionally omits exact throttling metrics to prevent teams from treating the slowdown behavior as a guaranteed service level.

Scheduled Apex does not support elastic limits because the feature trades execution speed for additional volume, which conflicts with the time-sensitive nature of scheduled runs. The author advises using the extra capacity strictly as a resilience buffer rather than a primary scaling strategy, recommending that organizations investigate root causes when they regularly approach baseline limits.

Read the original at Bob Buzzard Blog (opens in a new tab)

Worth reading?