Issue turning ON Replay Debugger

I am having a similar issue with version 44.7.0. I am connected to a Sandbox ORG and I am able to deploy from a project locally to the ORG, however when I am triggering the command SFDX: Turn on Apex debug log for Replay Debugger, I get the following error message:

{"message":"Provided external ID field does not exist or is not accessible: null","status":1,"stack":"NOT_FOUND: Provided external ID field does not exist or is not accessible: null\n at HttpApi.getError (C:\Users\luis_\AppData\Local\sfdx\client\node_modules\jsforce\lib\http-api.js:250:13)\n at C:\Users\luis_\AppData\Local\sfdx\client\node_modules\jsforce\lib\http-api.js:95:22\n at tryCallOne (C:\Users\luis_\AppData\Local\sfdx\client\node_modules\promise\lib\core.js:37:12)\n at C:\Users\luis_\AppData\Local\sfdx\client\node_modules\promise\lib\core.js:123:15\n at flush (C:\Users\luis_\AppData\Local\sfdx\client\node_modules\asap\raw.js:50:29)\n at _combinedTickCallback (internal/process/next_tick.js:131:7)\n at process._tickCallback (internal/process/next_tick.js:180:9)","name":"NOT_FOUND","warnings":["All --json output, including on error, is moving to stdout. Use the SFDX_JSON_TO_STDOUT environment variable to move over to the new functionality. This will become the default in version 45."]}

SFDX: Turn On Apex Debug Log for Replay Debugger ended with exit code 1

I am also able to download a debug log from VS Code but launching from the .log downloaded doesn’t do anything.

This is my launch.json:

{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "Launch Apex Replay Debugger", "type": "apex-replay", "request": "launch", "logFile": "07L3C000005c8RgUAI_20181119115110.log", "stopOnEntry": true, "trace": true } ] }

07L3C000005c8RgUAI_20181119115110.log is the downloaded log file.

[allileong]

Hi @lflorezcyberark, you should be able to launch the replay debugger if you use the full path to the log file instead of just the log’s file name ("logFile": "07L3C000005c8RgUAI_20181119115110.log",) in your launch.json file. Alternatively, you can also launch the replay debugger by right clicking anywhere on the open log file and selecting SFDX: Launch Apex Replay Debugger with Current File

[allileong]

Hi @lflorezcyberark, I believe I’ve found the issue and we are working on a fix. As a workaround in the meantime, could you try deleting all of your expired trace flags?