HomeHelp CenterAutomations & Workflows

Testing and troubleshooting workflows

Dry-run preview, run logs, and what to do when a workflow misfires.

2 min read · Updated Jul 4, 2026

Workflows run on real data, so testing them carefully matters.

Dry-run preview

Before activating, use the workflow's preview (dry-run) against a sample record. Tormano shows what would happen at each step without actually doing it — no emails sent, no fields updated, no tasks created.

Run logs

Once active, every workflow run is logged. Run logs are also retrievable through the public API. Each entry records the triggering record, each action's outcome (success / skipped / failed), any error message, and timing — so you can find and diagnose failed runs.

Common failures

  • Email action failed — usually a delivery issue (rate limit, or a suppressed/unsubscribed recipient).
  • Webhook timeout — the destination took too long. Make the receiving endpoint faster or reduce the payload.
  • Field update failed — usually a permission issue (the workflow's effective user can't write that field).

Pausing a live workflow

If a workflow is misbehaving, Pause it from the Workflows list. It stops firing until you resume it.

Rate limits

To prevent runaway loops, each workflow is capped by default at 100 executions per hour (higher on larger plans). If you hit the limit, fix the underlying cause rather than just raising the cap.