Testing, runs & debugging

Prove a flow works, then watch it run.

Test run

Use Test run to execute the flow against a sample shop without waiting for a real trigger.

Runs log

Every execution is logged with its status (completed / failed). Open a run for Run details:

  • The exact path it took, including branch decisions and per-step output ("Sent … to …", "Posted to Slack", "Skipped — …").
  • The trigger payload (copyable).
  • Any error, on the step that failed.

Debugging tips

  • A failed HTTP step shows the exact error on that step.
  • "Skipped" outputs explain why (e.g. no recipient, Slack not connected).
  • Re-run after fixing config.

Scheduling note

Runs are processed by a background worker; the daily triggers fire via the scheduler. Manual test runs execute immediately.