Hi Derrick,

Thank you for your question.

The behavior that you are describing might be related to the 2MB log file limitation in Salesforce - if you're trying to debug a large part of logic that generates more than 2MB of logs, Salesforce will truncate the log file thus you won't be able to debug the later stages of the execution flow. 

Can I please ask you to check if you can find the corresponding log entries (to the line of code that you are debugging) in your log file? And just to double-check and ensure - can you please confirm that the line of code where you have a breakpoint is 100% hit in the session that you're debugging?

In case if the 2MB limitation is the reason in your situation - the only solution is to try debugging smaller parts of your logic. You can debug smaller parts using Anonymous Apex, for example.

Looking forward hearing back from you.

Best Regards,

Vladimir

Thanks Vladimir.  It was the 2MB log file limitation. I will just use the anon apex when possible. Thank you for the explanation.

Derrick

Hi Derrick,

Thank you for getting back with the update - I'm happy that the Debugger works for you that way.

Please feel free to let us know if you'll have any other questions or ideas :)

Best Regards,

Vladimir

Hi

How do I actually go about having one of my breakpoints stop the code execution?

I've tried putting a breakpoint in a Unit Test and also in Anonymous Apex - the breakpoint appears to do nothing on both occassions...

Thanks

Adam

Hi Adam,

Thank you for your question.

Since this is a Retrospective Debugger, all the debugging actions are performed already after an execution that was performed previously on Salesforce. You can see that when you start debugging, for example, a unit test, the IDE run it, get a test result, and start the debugging after this.

This is why any of breakpoints couldn't affect an execution process and cannot abort it.

After running a debugging process, you can use your breakpoints to track the execution process that was already run.

You can find all the information about using breakpoints for you debugging process in the IDE and about the debugging process itself here and here.

Hope this would help.

Regards,

Kate

Thanks Kate!

As constructive critisism I found this confusing:

"Set the breakpoint next to the string that you want to explore in more detail"

When it says "string" it means "line of code" right?

Also if this article started by showing how to kick off debugging a unit test or anon apex I think it would help readers as they can try it out really quickly. For me it wasn't obvious how to kick debugging off.

Anyway, I've figured it out now and it's a great feature!

Thanks
Adam

Hi Adam,

Thank you for your response and I'm happy to hear that you like the Debugger functionality!

Also, thank you for sharing your confusions - we will take them into account and will be happy to make the documentation more clear and convenient for exploring the IDE.

Have a nice day!

Regards,

Kate