Test and monitor Automation flows

Run a controlled test of an active Automation, then inspect the steps that succeeded or failed. Test runs can send messages or change connected records. Use run history to see what happened.

Prepare a useful test

1. Save, publish, and activate the flow. Activation enables its configured trigger as well as Test run, so prevent unrelated events from reaching the flow during the test.
2. Choose input that represents a real event without exposing sensitive customer data unnecessarily.
3. Confirm that any contact, segment, broadcast, or connected account belongs to the current workspace.
4. Check whether an external action will create or update real data.
5. Select Test run, enter the input, and wait for the run detail. The test uses the active published version. Saving a draft does not include those edits in the test. To test changes, follow Change a live flow below.

Review each visited step, its resolved input, output, duration, and error. Also confirm that branches expected not to run were skipped for the right reason. If the run selects an audience, review its source, contact count, evaluation time, and state before trusting a later Broadcast step.

Read a failed run

Start with the first failed step or audience selection to find where the problem began. Common causes include a missing variable, an unavailable connected account, a saved segment version you cannot access, a rejected external request, or a current campaign safety check.

Retry only after deciding whether the failed operation is safe to repeat. A connected system may have completed work even when the response was interrupted. Check the flow’s duplicate-prevention setting and the external system’s record before repeating the action.

Change a live flow

Select Deactivate, edit and save the draft, resolve any issues, then Publish and Activate. Run a controlled test of the new version. You cannot publish while the flow is active. Previous run history remains available to show which version performed the work.

Archive a flow only when the team no longer needs to edit or activate it. Archiving does not rewrite historical runs.

Next: Manage integrations or review broadcast outcomes.