microsoft / microsoft/AL

Debugger "paused on exception", but no call stack or cause shown anywhere

Open
#8,013 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger input-needed
Dominant language
PowerShell
Stars
881
Forks
285
Avg merge
3d 36m
Merged PRs (30d)
1

Description

1. Describe the bug
In my case, after a onValidate trigger is finished, and before entering OnAftergeRecord on a Page, the debugger is stopping on an exception. It shows "paused on exception", but the call stack is empty, and there is nothing in the VARIABLES/Locals section. Without single stepping, this exception is still breaking the code execution and I have to continue manually (f5) - very annoying and not helpful in any way.

2. To Reproduce
Sorry, without any exception info, I cannot tell. I added a commit to see if this would cause the exception earlier, but no success.

3. Expected behavior
Either don't stop execution, or give any info on why the execution is stopped (other than there was an unnamed exception) - or give a way to skip/ignore "non critical and non informative" exception!

4. Actual behavior
Debugging is very time consuming when code execution is stopped, and only the little "paused on exception" info near the call stack even indicates execution is stopped.

5. Versions:

using latest vs code and AL extension / runtime 15.0 (used older runtime before, and had the same issue for month) / tried 25.x & 26.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files or tests and cannot provide a reproduction. Start by investigating the AL debugger behavior in Visual Studio Code around an onValidate trigger finishing before OnAfterGetRecord, using the listed runtime and extension versions; done means the pause is avoided or exposes a useful cause and call stack.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.