[SalesForce] VF Controller System.debug output not appearing in log file

I've got my Apex Code debug log level set to FINE (was DEBUG) and System debug log level set to FINE (was DEBUG). I'm still not seeing the result of my system.debug statements in the log file. I've also changed logging level on the system.debug statement to LoggingLevel.ERROR.

The code in question is initiated by a button press in a Visualforce page. Also, the log file has not been truncated.

What have I missed? Debugging apex when I can't get to my system.debug output is just about impossible.

Visualforce button code that calls the Apex method:

<apex:pageBlockSectionItem >
<apex:commandButton action="{!removeSelectedNow}" value="Remove Selected Now" rerender="tablepanel,tableblock,table,panelMsg" id="theRemoveBtn"/><p/>
</apex:pageBlockSectionItem>

Apex code:

public PageReference removeSelectedNow() {
system.debug(LoggingLevel.ERROR,'xyzzy-removeSelectedNow() - start');
...

Best Answer

When using a apex:commandButton with an action= attribute, SFDC will first decode the view state, then use the values from the form (or enclosing actionRegion) by calling the respective setters in the controller and then invoke the action method.

If the setters blow up with an uncaught exception, the action method will never get invoked and your debug statement will never appear.

This is all documented in the VF Order of Execution (excerpted below - you may be failing at step 2)

Related Solutions

[SalesForce] I’m unable to see system.debug statements on a trigger

Go to Setup->Monitoring->Debug Logs If your name is not appeared under Monitored user click on New and select yourself as a Monitored user and try again.

[SalesForce] Does anyone understand Debug Filtering

Here is the quick answer so you can hopefully get on with your day of debugging goodness.

Use Error rather than Info level logging.

System.Debug(LoggingLevel.Error, 'For the love of god, show up in the log!'););

You don't need to use "Set event filters for username" under Monitoring > Debug Logs > Filters. Just have the developer console open and set the ApexCode level to ERROR.

When you look at the Change Log Levels screen in the developer console what you are actually seeing is a UI over the TraceFlag records.

There are two records due to the two TraceFlag records that get created when the developer console is started. One will have the ScopeId set to the current User and the other will be empty for organization level logging. Note that it is also possible to create multiple traces for a single user, which results in multiple rows in the UI. Further rows can be created where the TracedEntityId is that of an ApexClass with LogFilter overrides (see below).

It might be worth checking for rogue records here. You can do this with SOQL in the Developer Console Query Editor by checking "Use Tooling API":

Select Id,IsDeleted,TracedEntityId,ScopeId,ExpirationDate,Workflow,Validation,Callout,ApexCode,ApexProfiling,Visualforce,System,Database from TraceFlag

You can safely delete them all (assuming you are the only dev in the org) and then let the developer console recreate them.

It would be worth checking if you have per Apex class logging level overrides on. This would appear under the Log Filters on the individual Apex Class.

enter image description here

If you are interacting with Salesforce via an external tool or the API it is possible the requests are overriding the logging levels. For instance, the DebuggingHeader in the older Apex API allows the logging levels to be explicitly set for that request.

As you found, Workbench offers the option to execute anonymous Apex with defined logging levels.

The FuseIT SFDC Explorer tool lets you explicitly define the logging levels that will be applied. (Full Disclosure: I work for the company that makes this tool)

Best Answer

Related Solutions

[SalesForce] I’m unable to see system.debug statements on a trigger

[SalesForce] Does anyone understand Debug Filtering

Related Topic