Choosing Between @future and Queueable Apex for Asynchronous Work
Decide when to use Salesforce @future methods versus Queueable Apex based on parameter types, job chaining, and monitoring needs.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide when to use Salesforce @future methods versus Queueable Apex based on parameter types, job chaining, and monitoring needs.
Enqueue asynchronous Apex jobs that accept sObjects and chain follow-up work, then monitor results in AsyncApexJob.
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.
Heap sizing for bulk Apex A design is being evaluated for bulk processing that keeps data in memory during an Apex transaction. The documented capability is the Apex heap size governor limit, which caps in-memory data per transaction and is enforced separately for synchronous and asynchronous contexts. Heap usage is measured per transaction and includes vari