Skip to main content

Troubleshooting Group Email Failures (CRM)

This guide details the essential troubleshooting steps to diagnose why automated email alerts (like Admissions Alerts) are failing to send to group aliases (e.g., staff@ or ur@ addresses) even though individual users receive the alert successfully.

Updated over 3 months ago


Q: Why is my Admission Alert Workflow sending to me, but not to my staff distribution list?

A: This is a common issue that almost always indicates a filtration block or denylist rule outside of the CRM itself (within your organization's mail system or our email delivery partner). When a group alias is sent too many automated messages, it can be automatically flagged as spam or inactive.


Q: What is the recommended step-by-step process to troubleshoot group workflow failure?

A: Follow these steps to isolate the issue to either the CRM trigger or the external mail domain filter:

Step

Action

Purpose & Expected Result

1. Verify Workflow Configuration

Ensure the workflow is set to trigger correctly (e.g., Intake Opportunity Updated). Verify the Email Alert action has the group address (staff@) listed as a recipient.

Expected Result: The workflow is active and configured correctly.

2. Check Outgoing Server Log

Log into the Outgoing Server platform (e.g., Mandrill or your email service dashboard) to view the sending logs for the specific time the workflow was supposed to fire.

Expected Result: Search for the email subject line. If you see a "Rejected," "Bounced," or "Deferred" status for the group address, the issue is external to the CRM.

3. Check for Bounce/Deny Status

If the log shows a rejection, check the Denylist/Bounce List within the Outgoing Server platform. If the group email is on this list, it will never receive emails.

Expected Result: The group is not found on the Denylist, or it is removed, allowing a resend attempt.

4. Check Internal Whitelist (Safe Sender)

Confirm with your internal IT department (or Google Admin/Office 365 Admin) that [email protected] is added to your organization's safe sender or Allow List.

Expected Result: The email domain is not blocking the CRM sender.

5. Test with a New Alias (Workaround)

Create a brand new distribution list (e.g., new_alerts@) and temporarily place it in the workflow recipient field.

Expected Result: If the new list works, the old group alias is permanently flagged, and the new one should be used as a workaround.


Pro Tips / Extra Help

Edit Workflow and Export Mandrill Activity - Step 3.png
Edit Workflow and Export Mandrill Activity - Step 7.png
Edit Workflow and Export Mandrill Activity - Step 9.png
Edit Workflow and Export Mandrill Activity - Step 21.png
  • Review the Dazos Safe Sender Article: Refer to the article on making Dazos a safe sender to ensure all IP addresses are whitelisted by your IT team.

  • Group Management is Key: If other Dazos workflows (like VOB alerts) are working for the group, but this specific workflow is not, the issue may be due to a specific rule within your organization's email filters that targets the subject line or content of the Admissions Alert email.


Related Resources

  • [How to Make Dazos a Safe Sender (Whitelisting Guide)]

  • [Guide: Configuring Workflow Email Alerts]

Did this answer your question?