R1D45 Queueable Apex
I am pretty sure that by the third week of any budding Apex developers journey they run into the following error in their code.
The help documentation does a decent job explaining what is happening. It turns out that if you have any DML in your code, you cannot make a "callout" (HTTP call) in the same method.Error: 'You have uncommitted work pending. Please commit or rollback before calling out.'
Unfortunately, there is no way to “commit” in Apex. What they really mean, is you need to do this step asynchronously. There are two ways of doing this. Using the @future annotation (I still have no idea how this works) or using Queueable Apex.
This allows you to essentially schedule jobs on a separate “thread” and not block the other parts of salesforce while your code runs.
The thing that threw me off was that I was not actually doing any DML in my code. My code is triggered with a DB trigger when a record is inserted or updated. I assumed that since the record was already inserted or updated then it would also already be “committed”, but this turns out to not be the case and I suppose this rule applies to anything that has to do with the Salesforce database.
Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.
Check out some more stuff to read down below.
Most popular posts this month
- My Custom Miniflux CSS Theme
- SQLite DB Migrations with PRAGMA user_version
- 2024
- 2023
- Ladybird on Debian Stable
Recent Favorite Blog Posts
This is a collection of the last 8 posts that I bookmarked.
- Pluralistic: AI "journalists" prove that media bosses don't give a shit (11 Mar 2026) from Pluralistic: Daily links from Cory Doctorow
- Avi Alkalay: Uniqlo T-Shirt Bash Script Easter Egg from Fedora People
- Offline 23 hours a day from Derek Sivers blog
- Pluralistic: California can stop Larry Ellison from buying Warners (28 Feb 2026) from Pluralistic: Daily links from Cory Doctorow
- On Alliances from Smashing Frames
- Acting ethically in an imperfect world from Smashing Frames
- Diffusion of Responsibility from Smashing Frames
- My AI Adoption Journey from Mitchell Hashimoto
Articles from blogs I follow around the net
Keeping sponsor lists up-to-date
Keeping sponsor lists up-to-date across multiple READMEs and websites is tedious - so I wrote a tool to automate it.
via Carlos Becker March 25, 2026Code as a Tool of Process
Steve Krouse wrote a piece that has me nodding along: Programming, like writing, is an activity, where one iteratively sharpens what they're doing as they do it. (You wouldn't believe how many drafts I've written of this essay.) There’s an incre…
via Jim Nielsen’s Blog March 24, 2026Paris's Bicycle Mayor and the Hormuz Shock
Why Energy Independence is an Enduring Antidote to Trump's Demented Chaos
via High Speed March 24, 2026Generated by openring