Breakpoints not hit for Batch Apex in Illuminated Cloud (Apex Debugger / Log Analyzer)

[akippiko]

Hello,

I’m having trouble getting breakpoints to hit when running a Batch Apex job.
  I can see the Batch Apex logs in Log Analyzer (Operation = Batch Apex, CODE_UNIT_STARTED for the batch class), and the log tree shows many runtime variables. The log file size is
  also large, so it looks like the execution is fully captured. However, when I click the bug icon to debug the log, breakpoints never pause and execution always runs to completion.

  Details:

  - Batch is triggered from UI (LWC action)
  - Debug levels: Apex Code = FINEST, Apex Profiling = FINES
  - Breakpoints set in Batch start/execute/finish
  - Log shows SimpleExporterScheduleBatch execution

  - IC = 2.3.8.8

  Question:
  What is the correct way to get breakpoints to stop for Batch Apex in IC?
  Do I need to explicitly start an Apex Debugger session before running the batch, and if so, how can I ensure it attaches to the Batch Apex transaction?

  Thanks.

[Scott]

Hi. The IC Apex debugger is log-based, so no need to start a session before running the process. You should, however, ensure that the logging levels are set sufficiently high for the user as which the process runs before it runs to ensure that the resulting log includes sufficient information for debugging. You can do that using Log Analyzer's settings. I know that you mentioned that everything was set to FINEST, but if it's only configured that way for the connection user and the batch process runs as another user, the log will likely be insufficient for debugging.

Assuming that's the case, IC should stop automatically at the beginning of the process when the log is loaded into Log Analyzer and triggered for debugging, and you should be able to set local breakpoints and have the IC debugger stop at those breakpoints. If you're not finding that to be the case, it would be useful to see a log where that's not happening properly. You can share it privately via email if you'd prefer. Note that my availability will be a bit choppy over the next few days due to the holidays, but I'll be happy to take a look at anything you send in the next several days and tell you what I'm seeing.

Regards,

Scott Wells