Launch, test, pause and stop a recipe
A recipe's page step by step — its settings, launching, the test e-mail, the discount code, pausing, resuming, re-activating after a change, and removing it.
Every recipe has its own page: Dashboard → Recipes → Preview all content, or Recipes and its card. Owners and admins of the workspace change it; members only see it.
Launch
- Open the recipe and read what it does. If a service it needs is not active, the page says Connect … to launch this recipe with Connect services →.
- Under Settings, check its values — each one shows its range, for example Quiet time before the reminder (minutes) 15–240. A recipe without values says This recipe has no adjustable settings — activation uses sensible defaults.
- Email language — English or Български, for this recipe's e-mails.
- Click Activate. The page says Setting up — the segment, the emails and the flow are being created; a few seconds later, Live — the recipe is running. You do not need to stay on the page.
The setup guide can launch several recommended recipes at once with Activate selected.
Launching does not e-mail the people who already match the recipe. A recipe starts with the people who enter its audience from now on — the next cart left behind, the next order — so switching one on never sends to your whole list at once.
Check it before customers see it
- Send test to me e-mails the recipe to your own address, with a sample cart, as soon as it is live. The test shows sample values instead of a real shopper's: Merge tags.
- Connected pieces links to what the recipe created: Flow ↗ in Automation, Email template ↗ in Push, Segment ↗ in CDP.
- Discount code — a recipe with a discount names its code, for example CART10, and says whether it is in your shop. Monfri creates the code itself only in WooCommerce. Otherwise the line says to create a code with exactly that name and that percentage in your shop — without it, the e-mail sends a code that does not work.
To change what an e-mail says, edit its template in Push: The e-mail editor. Re-activating keeps those edits.
Change the settings
Change the values and click Save & re-activate. Saving builds a fresh flow and updates the segment, so:
- changes made to the recipe's flow in Automation are replaced — the page warns first when it sees them (Customized or Edited in builder);
- people who were waiting between two messages in the old flow get no further messages from it;
- a value that widens the audience reaches the people who newly match within about two minutes. Lowering Days of inactivity from 60 to 30, for example, sends the win-back to everyone who has been quiet between 30 and 60 days. A jump of more than 200 people that is also more than a quarter of the current audience is held back as a likely mistake, and those people get nothing. Widen in small steps.
The workspace-wide recipe settings — quiet hours, the frequency cap, marketing consent — also reach a recipe only through Save & re-activate: Recipes.
Pause, resume, remove
| Button | What happens |
|---|---|
| Pause | It stops sending at once — Pause this recipe? It stops sending immediately; everything is kept and you can resume anytime. The flow, templates and segment stay as they are. |
| Resume | It is live again within seconds. Saving the settings of a paused recipe also resumes it. |
| Deactivate | Removes the flow and the subscription, with any changes made in the builder. You can launch it again later from scratch. |
A person who was between two messages when you paused gets nothing more if the recipe is still paused when their next message is due.
If something doesn't work
Needs attention · Repair
A pause or a removal did not finish, so parts of the recipe may still send. Click Pause again, or Re-activate to repair to rebuild it cleanly, or Deactivate.
Last error: …
The launch failed; the line says why. The most common reasons are in Recipe requirements. Fix it and click Activate again.
Test send failed
Push could not send it — usually the sender is not ready yet: Senders.