Definition
Full definition of dry run
A dry-run mode logs what each action would do without calling external APIs, which is critical when testing a new workflow against production data. Tiny Command does not have a dry-run mode today: testing a step runs it for real, so test against sample data or test accounts. Some actions (sends, charges, deletes) are especially dangerous to test live; dry-run lets you verify the data flow without side effects.
In practice
Dry Run examples
Dry-run output
Would call Stripe Refund with charge_id=ch_123, amount=1999 (skipped in dry-run)
Used by
Apps that exemplify dry run
See dry run in action across real integrations.
FAQ
Common questions about dry run
Does dry-run cost anything?
Usually not: in tools that offer it, actions are skipped, so no API quota is used. Some transforms still run to validate data shape.
Can I dry-run in production?
In tools that offer it, yes, and it is useful before a major change goes live: the workflow runs against real triggers but actions are skipped. Tiny Command has no dry-run mode, so test changes against sample data instead.
Learn automation, one term at a time
Get plain-English automation guides and templates in your inbox. No spam.