ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Queueable Apex is the underused middle ground between @future and Batch Apex: complex arguments, fresh governor limits, and job chaining — with one sharp fan-out limitation to design around.
Queueable Apex chaining splits large data processing into a sequence of jobs, each with fresh governor limits. A worked example, the limits that matter, and the mistakes that break chains.
Goal: Process 200,000 records efficiently while staying within Salesforce governor limits. Constraints: Batch Apex can handle up to 50,000 records per batch and allows a configurable batchSize , but requires careful start/execute/finish handling to avoid CPU and heap limits. Queueable Apex limits each job to 200 records and the system to 50 queued jobs per 2
A Salesforce team needs to run a long data-synchronization job that may need to stop before completion when an external system signals a timeout or cancellation. Batch Apex naturally partitions work into scopes and provides a finish method for finalization, while Queueable Apex supports chaining to avoid a single transaction timeout. The unresolved decision
salesforce