Mqttable
Back to docs

Replay Scenario: configure, Dry Run, and inspect Run Trace

How one saved scenario keeps source facts, settings, checks, Dry Run, and transient Run Trace evidence reviewable.

Jun 24, 2026Mqttable EngineeringMqttable Engineering

/replay/:scenario_id opens one saved local Replay Scenario in the Workbench.

Interactive diagram

Replay Source facts and settings beside Dry Run and Run Trace evidence.

Placeholder for the interactive diagram. Replace with the generated artifact when ready.

placeholder

Human job

  • Open a saved Scenario from its local Scenario tab.
  • Compare compact persisted source facts, target mapping, Replay settings, saved checks, and Dry Run output.
  • Run Replay and inspect the retained Run Trace for the current app session.

Automation handoff

  • Replay-specific MCP and CLI execution are not current product surfaces.
  • Use the Workbench for Dry Run, Run Replay, and Run Trace.

Boundary

The compact summary is not a full source-row archive. Run Trace and its execution feedback are transient in-memory evidence: they can disappear after app restart or pruning, and the Workbench does not expose report-history or professional-report export here.