Mqttable
Back to docs

Create a Replay Scenario from MQTT evidence

How Home, Proxy, PCAP, CSV, and demo sources become saved scenarios before Dry Run.

Jun 24, 2026Mqttable EngineeringMqttable Engineering

/replay/new opens the CSV/demo import modal. Home, Proxy, and PCAP evidence starts on its owning surface, where Mqttable resolves the current rows, saves one Replay Scenario, and opens /replay/:scenario_id.

Interactive diagram

Source evidence to saved scenario to target to dry run to run replay.

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

placeholder

Human job

  • Start from Home or Proxy TraceGrid, PCAP analysis, a TraceGrid CSV export, or the bundled demo.
  • Confirm the compact source facts, then select the target broker and adjust Replay settings when needed.
  • Run Dry Run before Run Replay. Creation already saved the Scenario; Dry Run is not a pre-save step.

Automation handoff

  • Replay creation, Dry Run, execution, and Run Trace currently live in the Workbench.
  • The standalone Remote-only CLI and current MCP tools do not create or execute Replay Scenarios.

Boundary

Source buttons do not carry row lists, payloads, credentials, or TLS private material in their URLs or values. A failed source build stays on the source page; a successful one opens the saved Scenario without forcing Replay settings open.