RStudio Debugger Breakpoints Fail to Trigger: Diagnostic Guide

You set a red dot next to an R line, but running the script completes without pausing. This usually is not an RStudio bug but a mismatch between how the code executes and how the IDE monitors the R process.

\n

Recognizable Condition

\n

The RStudio debugger breakpoint icon remains grey or is ignored when you run a script or R Markdown document. Execution proceeds past the breakpoint line without stopping.

\n

Diagnostic Table

\n\n\n\n\n\n\n\n

Symptom	Likely Cause
Script runs only via Rscript or terminal	Non-interactive execution bypasses the IDE debugger.
Breakpoint is greyed or on a non-executable line	The breakpoint is on a comment, blank space, or inside an inactive block (e.g., if(FALSE)).
No breakpoints work globally	Debugger is disabled in the .Rprofile via options("browserNLdisabled") = TRUE.
Breakpoints do not resolve in projects using renv or Packrat	The restored library lacks source code matching the breakpoint locations, preventing mapping.

\n

Ordered Checks

\n

\n
1. Verify execution method: Use the Source with Debugger button in the script editor. Avoid running scripts with Rscript or source() in the console if you need IDE-managed breakpoints.
\n
2. Check debugger options: In the RStudio Console, run options("browserNLdisabled"). If the output is TRUE, re-enable with options(browserNLdisabled = FALSE).
\n
3. Validate source mapping and environments: Run sessionInfo(), .libPaths(), and getwd(). Compare the R executable and library paths with those shown under Global Options > General > R version. Ensure the working directory contains the file with the breakpoint.
\n
4. Functional test: Create a minimal script with a breakpoint on the first executable line (e.g., x <- 1) and run it using the Source with Debugger button. If execution pauses, the IDE is functional; the issue lies in your script's structure or environment.
\n

\n

Fixes Tied to Findings

\n

\n
• If execution bypasses the IDE: Switch to RStudio's built-in run methods. Breakpoints will not trigger from Rscript or headless processes.
\n
• If the breakpoint is on a non-executable line: Move the breakpoint to a valid code line such as an assignment, function call, or expression.
\n
• If the debugger is disabled: Re-enable it by running options(browserNLdisabled = FALSE) in the console, or check your .Rprofile for suppressing settings.
\n
• If renv/Packrat library mismatches exist: Restore the correct package version or rely on project snapshots rather than disabling reproducibility tools.
\n

\n

Escalation Criteria

\n

If a minimal test script also fails to pause at a breakpoint, verify your RStudio version compatibility or perform a fresh installation. Persistent path mismatches across sessions may indicate a need to isolate the project in a dedicated container or contact RStudio support with sessionInfo() output.