Small and medium business | Business Central, N...

Answered

Suddenly, I found a breakpoint does not work!

(7) Share

Report

Posted on by 延哲-07060026-0

Hi experts!

Suddenly, I found a breakpoint does not work, though that was working before? What do you think happening on this apps?
Look forward to haring from you.
Nobuhara

--- app.json

{

"id": "c524b757-b1cf-4718-8a4a-101f54d1c6c3",

"name": "BreakpointTest",

"publisher": "Default Publisher",

"version": "1.0.0.4",

"brief": "",

"description": "",

"privacyStatement": "",

"EULA": "",

"help": "",

"url": "",

"logo": "",

"dependencies": [],

"screenshots": [],

"platform": "26.0.0.0",

"application": "26.0.0.0",

"idRanges": [

{

"from": 50100,

"to": 50149

}

"resourceExposurePolicy": {

"allowDebugging": true,

"allowDownloadingSource": true,

"includeSourceInSymbolFile": true

"features": [

"NoImplicitWith"

]

}

--- launch.json

{

"version": "0.2.0",

"configurations": [

{

"name": "Microsoft cloud sandbox",

"request": "launch",

"tenant" : "****************************",

"type": "al",

"environmentType": "Sandbox",

"environmentName": "sandbox2",

"startupObjectId": 22,

"startupObjectType": "Page",

"breakOnError": "All",

"launchBrowser": true,

"enableLongRunningSqlStatements": true,

"enableSqlInformationDebugger": true

}

]

}

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Suresh Kulla 50,243 Super User 2025 Season 2 on at

Like (5)

Report

I did experience this sometimes. You need to remove all breakpoints and try restarting VS Code. It will work.

Was this reply helpful? Yes No
Suggested answer

Saeed Nouman 14 on at

Like (3)

Report

You’re not debugging the same environment/tenant you think you are
launch.json targets environmentName: "sandbox2" and environmentType: "Sandbox" with a specific tenant.
If your browser session is signed into a different tenant/environment (or you open a different BC tab than the one VS Code launches), the debugger attaches to the wrong session and no breakpoints will bind.

Close all BC tabs.
In VS Code, run F5 (not Ctrl+F5) to publish & start a debug session.
Use only the browser tab that VS Code opens automatically—don’t switch tenants or tabs.
In BC Extension Management, confirm the installed version is 1.0.0.4 (matches app.json).
Place a breakpoint in a guaranteed-executed spot.
Trigger that code path. If it hits, your mapping is good—then move the breakpoint to your original location and verify that path is actually executed.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,329 Super User 2025 Season 2 on at

Like (2)

Report

Hi, just add some info.

In VS Code, you can create a shortcut to clear all breakpoints directly, which is very convenient.

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,136 Super User 2025 Season 2 on at

Like (3)

Report

Breakpoints only work if the extension is published in Debug mode. If it suddenly stopped, republish with debugging, make sure you’re on the right environment, and then try again. Sometimes it helps to remove all breakpoints and reload VS Code (Ctrl+Shift+P → Reload Window).

✅ Mark this as the verified answer if helpful.

Was this reply helpful? Yes No