GUIDE

Shiny debug mode

A dedicated mode for tracing reactive dependencies, spotting invalidation loops, and fixing UI/server mismatches.

Shiny debug mode in RCode

When to use it

  • Outputs that stop updating after a filter change
  • Observers firing twice on startup
  • Module namespace or ID collisions
  • Performance: reactives recomputing on every keystroke

Workflow

  1. Paste ui and server code into the context panel
  2. Select Shiny debug mode in the playground
  3. Describe the symptom — what you expected vs what happened

Related

Shiny use case · Launch blog post