When Automation does not work
The usual reasons a flow does not start, a step fails, a connection stops working, a recipe sends nothing or a run waits, and how to find the cause in a few clicks.
Start with the flow's runs — Flows → ⋯ → View Runs. A run that exists means the trigger worked and something later went wrong; no run means the trigger never fired: Runs.
The flow does not start
Check, in this order:
- Is it published? A flow runs only after Publish; a draft does nothing on its own.
- Is it on? The switch in Flows must be green.
- Is the workspace read-only? A red bar says Automations and sending are paused… — nothing runs until the plan is active: Plans, the trial and read-only.
- Does the trigger receive anything?
- Webhook — the other system must send a POST with the Secret in
X-Webhook-Secret; without it, it gets 403. - App event — for an app outside Monfri, its connection must be Active.
- Scheduled — check the Timezone: in UTC, 9 AM is noon in Sofia in summer.
- CDP event — the event must really arrive in CDP: Events.
- Webhook — the other system must send a POST with the Secret in
More on each trigger: Triggers.
A step fails
Open the failed run, click the red step and read its Error; its Input shows what it received.
| Error | Cause and fix |
|---|---|
| Unresolved flow variable {{ … }} | A value from a step that did not run or did not return it. Check the pill, and the branch it is on. |
| 401 / 403 from an app, or the connection turned Invalid | The key was changed or revoked. Edit the connection with a new key: Connections. Push's connection turns Invalid only on a 401, and Monfri renews it within the hour. |
| 403 from Push with a reason — trial has ended, Can send campaigns | Push refused on purpose; the connection is fine. The reason says what to fix: Steps in Monfri. |
| no confirmed default sender, not one of this workspace's senders, Sending domain is not verified | Push's senders: Steps in Monfri. |
| Pick why the deal was lost., The project id field is required. | CRM's rules: Steps in Monfri. |
| … blocked to prevent SSRF | An address on a private network. Use a public one. |
| Flow execution timeout | A slow app; turn on Retry on failure for that step. |
Fix the step, Publish, then Run Now or wait for the next event.
A recipe sends nothing
Open the recipe's page in the Hub: Recent activity shows whether anyone matches it, and the results show what was sent. Most often nobody new has entered yet, the people have no e-mail address, they unsubscribed, or Marketing consent for recipe emails is on and they gave none: Recipe requirements. Launching never e-mails people who already matched — a recipe starts with the next person who enters: Launch a recipe.
A run waits
- WAITING — in a Wait; it says when it resumes. Normal for recipes.
- WAITING after Send email — the trial's 200 e-mails a day are used up (it resumes after midnight UTC), or Push asked to slow down (up to an hour). The step says when it runs again.
- WAITING FOR THE AGENT — a Run agent step, up to 15 minutes.
- NEEDS APPROVAL — only old flows with the approval step, which is no longer offered; the run expires after seven days. Remove the step from the flow.
E-mails go out twice
Two flows do the same thing — often a recipe and a flow you built, or a duplicated flow left on. Search Flows for both, and switch one off. For order e-mails, your shop may send its own as well.
No access to Automation
- You don't have access to Automation in this workspace. Ask a workspace admin to grant it in Monfri. — your role has no Automation access: Service access.
- Automation is not set up for this workspace yet. A workspace admin can activate it in Monfri. — activate it: Open, activate and deactivate services.
Still stuck
Write to [email protected] with the flow's name and the time of the run: Getting help.