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
- 2024
- Reinstalling Windows at 1am
- SQLite DB Migrations with PRAGMA user_version
- My Custom Miniflux CSS Theme
- How to Disable Wayland in Debian Testing
Recent Favorite Blog Posts
This is a collection of the last 8 posts that I bookmarked.
- The Software Essays that Shaped Me from Refactoring English
- Give Your Spouse the Gift of a Couple's Email Domain from mtlynch.io
- Skip the Next iPhone from Articles on Jose M.
- Have smart glasses finally hit an inflection point? from The Torment Nexus
- The McPhee method from the jsomers.net blog
- Pluralistic: LLMs are slot-machines (16 Aug 2025) from Pluralistic: Daily links from Cory Doctorow
- Pluralistic: Bluesky creates the world's weirdest, hardest-to-understand binding arbitration clause (15 Aug 2025) from Pluralistic: Daily links from Cory Doctorow
- Just a Little More Context Bro, I Promise, and It’ll Fix Everything from Jim Nielsen’s Blog
Articles from blogs I follow around the net
On concrete examples
I had some great conversations via email over the past couple of weeks with a bunch of different people, discussing all sorts of things that I’ll for sure end up writing about. Today I wanted to briefly touch on the topic of examples, which was pa…
via Manuel Moreale — Everything Feed October 16, 2025Hacking Workshop for November 2025
For next month, I'm scheduling 2 or 3 discussions of Matthias van de Meent's talk, Improving scalability; Reducing overhead in shared memory, given at 2025.pgconf.dev (talk description here). If you're interested in joining us, please sign up …
via Robert Haas October 16, 2025Should we be afraid of AI? Maybe a little
Almost exactly a year ago, I wrote a piece for The Torment Nexus about the threat of AI, and more specifically what some call "artificial general intelligence" or AGI, which is a shorthand term for something that approaches human-like intelligence…
via The Torment Nexus October 16, 2025Generated by openring