I have subscriber access for the org and have also created debug logs for the particular classes I need logs for. However, the scheduled job that runs still has the logs obfuscated. I can see the debug logs for visualforce page access but not for the background job. Is there a difference for scheduled job vs managed code in terms of logging? How do I enable logs for the scheduled job?
My experience with the subscriber access debug logging via the LMA application has been that it only exposes log messages for requests that originated from that subscriber session.
I.e. Say both you and the user that granted you login access are connected at the same time. Debug logs that originate from your session will have the associated managed package logging exposed. Where as the logs that originate from the actual users session will not.
That does present a bit of a challenge for scheduled jobs. You could try using
system.schedule directly from the subscriber login session. However, I suspect this won't work. Worth a try though.
Maybe you can call the
execute method directly in anonymous Apex? It would depend on how it uses the
I've raised the idea Allow License Management App to expose managed package logging for entire org. It would help deal with edge cases like this and make accessing the log much easier.