Timeline for Too many SOQL queries: 101 and Triggers
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2019 at 15:50 | comment | added | David Reed | @OscarGonzalez I'm not familiar with that specific quirk, but it might be worthy of its own question. | |
| Feb 26, 2019 at 15:49 | comment | added | Oscar Gonzalez | We reduced batch size and solved the issue short term. But with more investigation, noticed a strange behavior. When the native duplicate matching rules were enabled, when doing the convert from Lead to Contact, the associated triggers were receiving single entities instead of batches, but when the Duplicate matching rule was disabled, the triggers were suddenly getting the full batches like one would expect. Do you have any idea what could be causing that behavior? | |
| Feb 20, 2019 at 14:54 | vote | accept | Oscar Gonzalez | ||
| Feb 19, 2019 at 14:29 | comment | added | David Reed | @OscarGonzalez No, Salesforce does not coalesce DML operations across separate API calls. The API call bounds the transaction. | |
| Feb 19, 2019 at 14:25 | comment | added | Oscar Gonzalez | So if I inderstand correctly, every instance of Upsert that I do outside of Salesforce will be treated as it's own transaction, right? There isn't some sort of system where multiple upserts in a small period of time get compressed into a single transaction or anything of the sort then? If so, I will try for the short term to reduce the batch sizes being sent to Salesforce and see if that stops it while also trying to find what is generating so many queries. Thanks. | |
| Feb 19, 2019 at 13:03 | history | answered | David Reed | CC BY-SA 4.0 |