apex-async-patterns

Salesforce asynchronous patterns like Batch Apex and Queueable handle large data volumes by processing records outside the main transaction, bypassing governor limits. Batch Apex processes data in manageable chunks, while Queueable handles smaller workloads and enables chaining for multi-step workflows.

Use Queueable for asynchronous processing when you need job chaining, callout capabilities, or non-primitive parameter types. Future methods are suited for simpler, isolated tasks with primitive parameters. Queueable provides better monitoring and structured execution for complex multi-step workflows.

To schedule and chain Apex jobs, use Schedulable to trigger execution at specific times and Queueable for sequential data processing pipelines. Chaining Queueable jobs allows one job to initiate the next, orchestrating multi-step workflows while respecting governor limits and maximum active batch constraints.

Salesforce async processing supports HTTP callouts from Queueable contexts by implementing the AllowsCallouts interface. Batch Apex also supports callouts by implementing Database.AllowsCallouts, enabling safe integration with external services during long-running data processing pipelines.

Limitations of chaining Batch Apex jobs include a maximum of five active queued or concurrent batches per org, restrictions on calling future methods from batch contexts, and chain depth limits. Queueable is recommended for sequential chaining to avoid hitting these governor limit constraints.