Skip to main content

Campaign statuses

Campaigns show a status tag that tells you whether the campaign is running and, when something goes wrong, why. The two campaign systems use different status sets, so this page keeps them separate: Flows campaigns on Campaigns > Flows, and the legacy Python campaigns on Campaigns > Python.

In both systems the status appears as a colored tag in the campaign list and in the campaign header, and the action button next to it changes with the status. Hover over the tag to read its message — for an Error, the message names the cause.

Flows campaign statuses

A Flows campaign processes triggers and schedules communications only while it is Active. New campaigns start as Inactive. You move between Inactive and Active with the Start / Stop button in the campaign header.

StatusColorMeaningHow it gets hereWhat to do
InactiveAmberThe campaign is not processing events. Flows and data can be edited.A new campaign is created here, or you clicked Stop.Build and activate a flow, then click Start.
ActiveGreenThe campaign is running: triggers fire and communications are scheduled. The active flow is read-only.You clicked Start with at least one flow active.Monitor the Participants and Analytics tabs. Click Stop to edit again.
ErrorRedThe campaign hit an error and cannot proceed.A problem during processing — most often a channel that is not running or an agent that is stopped or in Error.Hover over the tag to read the message, fix the cause, then click Start. See below.

Only Inactive campaigns can be started, and only Active campaigns can be stopped. There is no separate pause action — Stop returns the campaign to Inactive and makes flows editable again.

Recover a Flows campaign from Error

  1. Hover over the Error tag to read the message — it carries the most recent error for the campaign.
  2. Check the channel the campaign sends through in Settings > Channels and confirm it is running.
  3. Check that the agents used by the flow's communication actions are running and not in Error — see Agent statuses.
  4. Fix the cause, then click Start to return the campaign to Active.

For the full start, stop, and troubleshooting workflow, see Flows.

Python campaign statuses

A Python campaign moves through a fixed lifecycle as you configure it. It runs only while it is Running, and the Start / Stop button changes with the status.

StatusColorMeaningHow it gets hereWhat to do
CreatedGrayThe campaign exists but is not ready to run — contacts or a Data Load strategy are still missing.A new campaign is created here.Add stages, upload a Data Load strategy, and upload contacts.
ConfiguredOrangeThe campaign has contacts and a Data Load strategy and is ready to start.The campaign has both contacts and a Data Load strategy.Click Start to begin processing contacts.
RunningGreenThe campaign is processing contacts and sending communications in their planned time windows.You clicked Start on a Configured campaign.Track progress on the Contacts tab. Click Stop to pause.
ErrorRedThe campaign cannot proceed.A problem during processing.Hover over the tag to read the message, then Force stop and fix the cause. See below.

The button reads Start for Created and Configured, Stop for Running, and Force stop for Error. Start stays unavailable until the campaign has contacts. There is no separate restart action — click Stop, then Start.

Recover a Python campaign from Error

  1. Hover over the Error tag to read the message.
  2. Click Force stop to halt processing.
  3. Fix the cause — open Show Logs from the header to read the campaign engine log, including strategy output and exceptions.
  4. Click Start to run the campaign again.

For the full setup, start, and stop workflow, see Python campaigns.

Notes

  • A Python campaign stays in Created until it has both contacts and a Data Load strategy; only then does it become Configured and ready to start.
  • The status tag in both systems carries a message. For an Error, hover over the tag to read it before you start troubleshooting.
  • These campaign statuses are separate from the per-communication statuses tracked inside a campaign — those are listed on the Flows and Python campaigns pages.

Was this article helpful?