Queueable Apex That Survives Retries
Queueable Apex becomes reliable when jobs are treated as at-least-once work: use idempotency keys, durable checkpoints, bounded retries, and outcomes you can inspect.
3 posts in this channel.
Queueable Apex becomes reliable when jobs are treated as at-least-once work: use idempotency keys, durable checkpoints, bounded retries, and outcomes you can inspect.
Summer '26 adds elastic async limits for Queueable and future jobs. The real opportunity is to shed low-priority work before the extra headroom runs out.
I have been using Apex cursors since they became generally available, and this is where they help in day-to-day Salesforce work.