Send Test Email Error in Campaign's Email step: An error occurred, please try again
Workflow Automation Send Email Trigger Action Not Firing A quick checklist for the most common reasons a Send Email action in a workflow silently fails…
2 min read468 words3 explained imagesUpdated Wed, 1 Jul at 5:36 AM
Assistants need to reach this page over the internet. While it is only running on your machine, these two buttons will not be able to load it.
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
Workflow Automation
Send Email Trigger Action Not Firing
A quick checklist for the most common reasons a Send Email action in a workflow silently fails to fire.
Overview
If you see the error below, or the Send Email trigger action just isn't firing, work through the checks in this article to find and fix the cause.
1The Error
If you see this error message, or the Send Email trigger action is not firing at all, work through the checklist below.
Buttons and menus referenced
missing }overusing {{{
2Troubleshooting Checklist: Please Check If…
Check 1
Merge field syntax in the email/SMS content
Check the email or SMS content for a missing } or for overusing {{{.
Check 2
Custom values are valid
Especially the links — see the list of valid custom values.
Buttons and menus referenced
missing }overusing {{{
Check 3
Email addresses are valid
For example: test@gmail,com with a comma instead of a dot will cause the action to fail.
Check 4
The From field is a valid email address format
For example, change ABC company to its actual email address, like info@abccompany.com.
Buttons and menus referenced
missing }overusing {{{
3FAQ
Q: What does "missing }" or "overusing {{{" actually mean?
Merge fields use double curly braces, like
{{contact.first_name}}. If a closing brace is missing, or if there's an extra opening brace (three instead of two), the parser can't resolve the merge field and the action fails to fire.Q: Where do I find the list of valid custom values?
See the list of valid custom values linked in Check 2 above — it covers the supported syntax and naming.
Q: Will one bad custom value break the whole email, or just that line?
A single invalid or malformed custom value can prevent the entire action from firing, not just the line it's on. That's why it's worth checking every merge field and custom value in the email, not just the ones you suspect.
Q: Does the From Name need to match the From Email exactly?
No, but the From field itself must contain a properly formatted email address — not a company name or plain text. A display name alongside a valid email is fine; a name with no email is not.
Q: I checked all four items and the email still isn't sending — what next?
Double-check the workflow's trigger conditions and any preceding steps that might be preventing the contact from reaching this action, then reach out to support with the workflow name and a screenshot of the error for further investigation.
Q: Does this checklist apply to Send SMS actions too?
Yes — merge field syntax and custom value validity (Checks 1 and 2) apply the same way to Send SMS actions. Checks 3 and 4 are specific to email since they involve email address formatting.
Was this guide helpful?
Related guides
How to check logs for a specific email in Mailgun3 min read · 8 imagesHow to fix links in the email that do not open?5 min read · 7 imagesWhen email replies are not showing up in Conversation4 min read · 5 imagesTroubleshooting Warning: Please contact your agency to change email settings2 min read · 4 images