2021.1

If an error is thrown, the rest of the current script is skipped and execution continues with the
next script.
In the call stack, frames are ordered from new to old, top to bottom. The current stack frame has
an arrow indicator. You will only see multiple stack frames if execution is suspended inside a
function.
You can click a frame to make it the current frame. The Variables panel always reflects the state
of the current frame. Note that this does not move the instruction pointer. The script remains
suspended at the most recent frame, even if that frame is not the current frame.
Source code
You can click any script at the left to view it in the source editor at the top right. An instruction
pointer in the left margin marks the current line.
The code is read-only, but clicking to the left of a line of code adds a breakpoint to it (except
when a line has no debuggable content, for example if it only contains a declaration or
comment). Note that breakpoints are discarded when the dialog is closed.
Hovering over a variable in the code shows the value of that variable. If the variable is nested,
like fields in record.fields, you can click on the variable, its parent, child elements and/or
siblings (if any) to see their value.
The value is read-only, but you can select it and copy it with Ctrl+C.
Find code
To search for a text in all of the scripts, starting with the currently selected script, press Ctrl+F
and start typing the text. While the Find field is visible, you can either use the arrow buttons next
to it, or press Enter / Shift+Enter to go to the next or previous match, respectively.
When the Find field is not visible, you can press F3 / Shift+F3 to go to the next or previous
code that matches your last search text.
Tip
When you click on an identifier (such as a variable name) in a script, the overview ruler at
the right highlights all other occurrences of that identifier straightaway.
Page 990