function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Anuj Thakur 4Anuj Thakur 4 

we are invoking a method by Queueable Apex. but while executing this method, no debug statements are printing.

Hi,
I am 2 question here Please provide your views  on below questions.
1.
we are invoking a method by Queueable Apex. but while executing this method, no debug statements are printing. Is there any feature of Queueable that if we  will execute any method from queueable, Debug statements can be printed or not as this is Asynchronous Apex?
2.

There is a variable called "VariableSetting". but its not defined anywhere in code. Also, its using in code like VariableSetting.SOMEVARIABLENAME which returns Boolean values. But if i am trying to print on "VariableSetting" it says error: "variable does not exist". Could someone suggest on this.

Any suggestion will be appriciated.

Vinod ChoudharyVinod Choudhary
Hi Anuj,

1. Batch jobs are asynchronous so, it may take some time depending on system load. It creates separate file for execute and finish call.
Also make sure that you have setup debug logs for current logged user in Monitoring > Debug Logs.
 
 You need to set up "User Trace Flags" with debug level for apex:DEBUG, system:DEBUG to see logs.

Please refer below link for the same.
http://salesforce.stackexchange.com/questions/98907/apex-batch-jobs-logs

2.  About VariableSetting. That you need to check where it's define in your Apex. I think it's somewhere is created in your class or extended class.


Hope this helps you!

 
Anuj Thakur 4Anuj Thakur 4
Hi Vinod,
Thanks. but I have already set up my debug logs. but we did not get any debug log printing in logs. I am clueless why it is not printing. 
2. We have checked in whole project code but its not defineing anywhere. is there any functioanlity that its has been defined in configuration somewhere?
Manj_SFDCManj_SFDC
At times if the debug log size is huge  you may face this kind of issue, you can try to use system.assert instead of system.debug