Skip to content
Doppelganger logo

Monitoring and Debugging

Monitoring and debugging are built directly into the system so you can always see what happened, when it happened, and why it happened. Every execution is recorded automatically, making it easy to diagnose issues and verify behavior without adding extra logging logic.

Executions Tab#

All runs are saved in the Executions tab in the sidebar.

Each execution includes:

  • Full execution logs
  • Captures during that run
  • Final data
  • A timestamp for when the run occurred

Executions are always saved, even if a run fails. This means you can safely debug after the fact without rerunning workflows.

Captures Tab#

Visual debugging is available in the Captures tab.

This tab stores:

  • Screen recordings
  • Screenshots
  • Browser state captures

Captures are automatically saved for every execution and are never deleted unless you manually clear them. This lets you see exactly what the browser saw at any point in time.

Why This Matters#

With executions and captures always available:

  • You can replay failures visually
  • You can trace issues to a specific timestamp
  • You can compare successful vs failed runs
  • You can debug without adding console logs or extra blocks
  1. Open the Executions tab
  2. Select the execution by timestamp
  3. Review logs and block output
  4. Open the Captures tab for visual context
  5. Fix the workflow and rerun

Summary#

Monitoring and debugging are automatic and persistent. Every execution is logged, timestamped, and paired with screen recordings and screenshots, giving you full visibility into workflow behavior with zero setup required.

Previous
Next