Timeline for Made 3500 SOQL Queries in one context. LIMITS HACK?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2022 at 2:16 | answer | added | sfdcfox♦ | timeline score: 1 | |
| Feb 3, 2022 at 15:59 | comment | added | codeulike | @YevhenKharchuk whether its synchronous or not has nothing to do with whether or not it is a transaction. The emails are acting a bit like Visualforce page renders in this context. so its a bit like rendering 35 visualforce pages, each with 100 SOQL queries on it. Nice experiment though! Eventually you will hit the email limit I guess! | |
| Dec 19, 2019 at 15:07 | comment | added | identigral | From Apex transactions: The boundary of a transaction can be a trigger, a class method, an anonymous block of code, a Visualforce page, or a custom Web service method . | |
| Dec 19, 2019 at 7:22 | comment | added | Yevhen Kharchuk | Result of calling renderStoredEmailTemplate is returned synchronously. It's not a separate transaction. | |
| Dec 18, 2019 at 19:00 | comment | added | identigral |
If each call to Messaging.renderStoredEmailTemplate is a separate transaction, the per-tx limit of 100 SOQL queries is still good. Does it complain if you go over 100 in the controller?
|
|
| Dec 18, 2019 at 5:26 | comment | added | Yevhen Kharchuk | @identigral I would say Salesforce limits should apply to every synchronous query in a context. | |
| Dec 15, 2019 at 23:33 | comment | added | identigral | What would be the non-buggy expected behavior, in your opinion? | |
| Dec 9, 2019 at 6:00 | history | tweeted | twitter.com/StackSalesforce/status/1203917322366390274 | ||
| Dec 8, 2019 at 21:07 | history | asked | Yevhen Kharchuk | CC BY-SA 4.0 |