Fix the Error: sf_devops:Too many SOQL queries: 101 issue in Salesforce with real causes, sample code, and proven solutions to stop SOQL limits from breaking your process. Our DevOps Live Support Team is always here to help you.
How to Actually Fix Error: sf_devops:Too many SOQL queries: 101
When the Error: sf_devops:Too many SOQL queries: 101 message pops up, your entire Salesforce flow stalls. It usually hits at the worst time, right when you’re inserting a batch of records or pushing an automation update. Although it looks scary, this error is simply Salesforce telling you that your code fired more than 100 SOQL queries in a single execution context.
But here’s the real story behind it, and more importantly, how you fix it without breaking your existing logic.
Why This Error Happens
The Error: sf_devops:Too many SOQL queries: 101 generally shows up when your code is not bulk-ready. For example, if someone inserts more than 200 records and your code contains a SOQL call inside a loop, Salesforce quickly hits the limit.
Here’s the classic mistake:
For(Account acc: Trigger.new){
for(Contact con:[select id from contact where accountId = :acc.Id]){
}
}This code works fine with a few records. However, once the volume hits a few hundred, Salesforce throws the Error: sf_devops:Too many SOQL queries: 101 because every loop creates a new SELECT statement.
Furthermore, triggers that update the same object again can also cause recursion, which fires SOQL repeatedly. Additionally, multiple flows, processes, or Apex handlers running in parallel can bump into the same limit.
Real Fixes That Actually Work
1. Move SOQL Outside the Loop
This is the first and most important fix.
Instead of querying inside a loop, fetch everything in one go:
Map<Id, Account> accountMap = new Map<Id, Account>(
[SELECT id, name, (SELECT id FROM contacts)
FROM account
WHERE id IN :trigger.newMap.keySet()]
);
for(Account acc : accountMap.values()){
for(Contact con : acc.Contacts){
}
}This reduces hundreds of queries into one.
2. Bulkify the Trigger + Handle Recursion
A surprising number of SOQL errors happen because developers split logic across multiple triggers. Always follow a trigger framework and control recursion with a static variable.
This prevents triggers from calling themselves in loops.
3. Offload Heavy Logic to @future
When logic isn’t time-critical, shift it:
@future
public static void processData(Set<Id> recordIds){
// Heavy SOQL and DML safely executed here
}As a result, your SOQL limit increases from 100 to 200.
Get Expert Salesforce Help Now!
4. Merge Queries to Reduce SOQL Count
Instead of making four separate calls:
Opportunity op = [select StageName, Account.OwnerId from Opportunity where id =:opId];
List<OpportunityLineItem> olis = [select id, productId from OpportunityLineItem where OpportunityId =:op.Id];
Account acc = [Select name, id from Account where id = :accid];
List<Contact> lstConts = [Select firstName, LastName from Contact where accountid = :accid];Merge when possible:
Account acc = [Select Id, Name,
(Select id, firstName, LastName from Contacts)
From Account
where id = :accid];This single query replaces four.
Conclusion
The Error: sf_devops:Too many SOQL queries: 101 isn’t a dead end. Once you reorganize your logic, bulkify your trigger, and avoid SOQL inside loops, the issue disappears for good. And because Salesforce will never increase these limits, rewriting code smartly is the only real solution.
If this error keeps showing up, you’re definitely dealing with hidden recursion, missing bulkification, or scattered automation. Fix those, and the Error becomes a thing of the past.
