How to fix LIMIT_EXCEEDED in Salesforce deployments

What it means

The fix

1. Bulkify the code path hitting the limit
   Rewrite the trigger, class, or test to operate on collections instead of individual records, cutting SOQL and DML calls per transaction.

   // Bad: SOQL inside a loop
   for (Account a : accounts) {
       List<Contact> cons = [SELECT Id FROM Contact WHERE AccountId = :a.Id];
   }
   
   // Good: one query outside the loop
   Map<Id, List<Contact>> conMap = new Map<Id, List<Contact>>();
   for (Contact c : [SELECT Id, AccountId FROM Contact WHERE AccountId IN :accountIds]) {
       if (!conMap.containsKey(c.AccountId)) conMap.put(c.AccountId, new List<Contact>());
       conMap.get(c.AccountId).add(c);
   }

2. Reduce test data volume to the minimum needed
   Scale back Apex test setup to the smallest data set that still exercises the logic being tested.
3. Check org limits before large deployments
   Review API and other daily limits in Setup before running a bulk data load or deployment that adds to usage already consumed that day.