You need to sign in to do that
Don't have an account?
Nadia
"maximum trigger depth exceeded" and other errors
Hi, I have wrote my code following documentation to adjust it to governors and limits restrictions. After deployment we get "maximum trigger depth exceeded" exception. I am pretty sure I do not have any recursive triggers, and I can't think of anything else I can do to diminish number of DML and SQL statemetns. (I do not have them inside loops). I tried to replicate the error by creating large number of records in test, and now I get System.Exception: Too many SOQL queries: 21. I dont know if this is what is causing "maximum trigger depth exceeded" in production. I cant replicate the original error.
I am now wondering if it might be so that it is not possible for us, since we are updating very large sets of records at a time using API - possibly hundreds of thousands. Could it be that APEX is just not the solution with such big data sets, or am I doing something wrong?
Message Edited by Nadia on 03-20-2008 10:25 AM
I am now wondering if it might be so that it is not possible for us, since we are updating very large sets of records at a time using API - possibly hundreds of thousands. Could it be that APEX is just not the solution with such big data sets, or am I doing something wrong?
Message Edited by Nadia on 03-20-2008 10:25 AM
When I am testing with multiple inserts (10) I see in the test log that number of SOQL queries gets incremented after each call to a trigger (update and insert), so when it reaches 21 it blows up. Does this mean I can not call insert operation more than 10 times if I have update and insert triggers on that operation with one SOQL query each?
I am quite confused of how should I proceed. Please help!
Message Edited by Nadia on 03-20-2008 10:24 AM