Sunday, 5 January 2014

MAXIMUM DEBUG LOG SIZE REACHED

*********** MAXIMUM DEBUG LOG SIZE REACHED ***********

Many Times i get frustrated when i want to log something and see the values in debug log and when i encounter an error saying MAXIMUM DEBUG LOG SIZE REACHED.

We all know the log levels in SFDC can be configured and hence setting filters as below in debug logs help to solve the problem

  • Database : NONE
  • Workflow : NONE
  • Validation : NONE
  • Callouts : NONE
  • Apex Code : ERROR
  • Apex Profiling : NONE
  • Visualforce : NONE

The above stackexchange link helps to identify how to solve the problems .

But when it comes to the TEST classes sometimes when there are too many test methods even filtering as shown above does not help much .How do we solve the problem then ?

One solution is to comment out all other test methods except the method that's giving trouble or suspected of cause of error .Hence we will be able to display logs for only the method and debug the result .


Introducing Lightning Base Components

Lightning Base Components are great addition to the platform and in fact revolutionary .One of the concerns around lightning component ...