Offline Debugger using action type not working consistently

Issue #1708 resolved
Matej Mercina created an issue

I’ve just been playing around with the offline debugger tried out the Apex/SOQL action type, however I cannot get this to work correctly. It appears as though I need to set the breakpoint several times before it starts working. For example, I’d get this message

21:05 Checkpoint reached at WSHelper:9
Heap dump = true
SOQL query = false
Anon Apex = false

Desipide the fact that the breakpoint does in fact have SOQL option selected and a SOQL statement defined.

And in the case of Apex, once it starts working the log does indeed report the action:

Execute Anonymous: Datetime dt =;
Execute Anonymous: dt = dt.addDays(3);
Execute Anonymous: System.debug('dt: ' + dt);

But I cannot get the debugger to stop there, It will just go straight to the end with the message

21:10:21.320 (320185859)|CUMULATIVE_PROFILING_END
ERROR: unbalanced stack frames.
Process finished.

I feel like I may be missing something here, but the documentation is unfortunately scarce.

Comments (3)

  1. Scott Wells repo owner

    Hi. "Unbalanced stack frames" means that something in the log couldn't be parsed as expected. The most common reason for that is a log that is truncated somewhere resulting in unpaired log entries, though it's possible that it's just some log format that IC isn't expecting or a bug in IC's log parser. The easiest way to get to the bottom of this would be if you could email the actual log to, but if that's not possible for reasons of privacy, let me know and we'll figure out another way to tackle this.

  2. Scott Wells repo owner

    This ended up being an issue with the debug logs emitted by Salesforce when an Apex script action is used. Nothing for IC to do here.

  3. Log in to comment