113
votes
Accepted
Error while updating debug log trace flag
I have faced this issue, which I fixed it by deleting all debugs logs from developer console.
In dev console, Select tab "Query Editor" at the bottom of the console
Select check box "Use Tooling API"...
12
votes
Error while updating debug log trace flag
The short term solution is to keep playing whack-a-mole~ApexLog as Pranay has suggested.
Longer term, the problem comes back to the Summer'18 update Store Larger Debug Logs with Changed Log Limits:
...
12
votes
Accepted
How to get running class and method names programmatically?
Here's a fun fact to get the ball rolling: the constructor for any Exception class will generate the current stack trace (no need to throw). So you can, for instance, get the stack trace in your ...
8
votes
Accepted
Exeception line numbers are not reliable
As you have demonstrated, this is a bug.
The resulting System.NullPointerException should have a line number reference back to the is statement line on line 3.
Please raise this as a support case and ...
8
votes
Salesforce Developer Console - Getting a stack trace easily
@NSjonas answer is good. I thought I'd add some more options.
System.debug
It's not ideal, as you need to modify the code to use it. Try something like:
System.debug(LoggingLevel.Error, new ...
7
votes
Salesforce Developer Console - Getting a stack trace easily
If you go to set log panels and select "Execution Stack" and "Execution Log", it should bring up a stack trace panel next to the standard log panel. Clicking any line in the Log Panel will load up the ...
5
votes
Accepted
Latest on reviewing errors in a managed package
As described in your link1, full stack trace information is only available when you login to the org via the LMA. And this option is only available if your app has passed a security review. So getting ...
3
votes
Accepted
Rewriting Try + Catch{System.Assert(false, 'blahblah')} for easy toggle-off of catch?
Take a look at An Introduction to Exception Handling.
For the record, I think there are better approaches to error handling than hiding the root cause. Personally, I would rather see Duplicate Value ...
2
votes
Accepted
Stack trace reference in Salesforce Commerce Cloud
See the Development Setup module found in the nav under Administration > Site Development. Within the "WebDAV Access" section, you'll see a subsection for "Log Files". There are two ways to access ...
2
votes
Managed Package: Catch exception and then re-throw asynchronously?
I don't have a managed package I can test with, though I suspect the stack trace will remain obfuscated. However, it certain does send an email and transfers the stack trace correctly:
public class ...
1
vote
System.LimitException: ivybat:Too many SOQL queries: 101 - Stack Trace
As per David Reed's answer, the issue is reported against processing in the ivybat managed package and you cannot debug that - only the supplier of the package can.
However, the issues could, in ...
1
vote
System.LimitException: ivybat:Too many SOQL queries: 101 - Stack Trace
This failure is in a managed package with the namespace ivybat. The managed package is installed in your org.
You can't debug managed package code, although you may be able to guess your way to a ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
stacktrace × 14apex × 7
exception × 5
debugging × 5
managed-package × 4
isv × 2
visualforce × 1
trigger × 1
unit-test × 1
error × 1
governorlimits × 1
sandbox × 1
error-messages × 1
developer-console × 1
package × 1
regular-expressions × 1
namespace × 1
logging × 1
debug × 1
debug-logs × 1
commerce-cloud × 1
try-catch × 1
limitexception × 1
apex-debugger × 1