Lev Lazinskiy

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.

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.