What’s “dry-run” mode and why use it?

Dry-run mode executes automation logic without actually sending emails:

How it works: Triggers fire and are processed normally. Conditions evaluate and paths are selected. All steps execute except final email send. Logs record what would have happened.

Benefits: Validate complex logic without sending test emails. Process large trigger volumes to test system performance. Identify issues before they reach recipients. Verify timing and conditions in realistic scenarios.

Use cases: Testing new automations before activation. Validating changes to existing flows. Load testing with production-like volume. Debugging issues in safe environment.

Limitations: Does not test actual email delivery. Cannot verify recipient experience. May miss send-time issues.

Best practice: Use dry-run for logic validation, then live test with seed lists for send validation.

Dry-run shows the automation's decisions. Live testing shows the complete recipient experience.