Skip to content

Debug Session Does Not Break at Breakpoint When Assigned in batch.execute Method #7310

@PieterJacob

Description

@PieterJacob

Summary

Whenever you start a debug session using the replay debugger, the session does not stop at any breakpoint when placed inside a batch execute method.

Steps To Reproduce:

For example...

  1. Create a unit test that executes a batch. Make sure that the execute method has some code.
  2. Create a log file of the transaction executed in step1.
  3. Put a breakpoint somewhere in the execute method of the batch.
  4. Start a debug session based on the .log file choosing SFDX: Launch Apex Replay Debugger with Selected File
  5. Verify that the debug session does not stop at the breakpoint.

If the execute method contains a call to a class method and a breakpoint is placed there, the debug session does stop there.

Expected result

  1. The debug session should stop at the breakpoint in the execute method.

Actual result

The Debug session does not stop and automatically ends.

Salesforce Extension Version in VS Code:

Salesforce CLI Version:
@salesforce/cli/2.131.7 darwin-arm64 node-v22.22.2

OS and version:
macOS Tahoe 26.3 (25D125)
VS Code version:
1.118.1 (Universal)
Most recent version of the extensions where this was working:
I don't remember if this ever worked. I have used Windows before, and there I have also noticed the same behaviour.

Metadata

Metadata

Assignees

No one assigned

    Labels

    waiting for userUse this label when you are waiting for some action to be taken by the user

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions