We are running into ongoing challenges with workflow “automation issues” tied to internal email notifications.
We have several workflows that send internal email notifications to multiple user-based properties within a single action, such as Deal Owner, Ticket Owner, Project Manager, and Designer. In many cases, one or more of these recipients has disabled workflow email notifications in their user settings. This is typically intentional, as those individuals prefer to monitor activity through properties, dashboards, or reporting instead of email.
Because of this, the workflow is flagged with an “automation issue,” even though the workflow itself is functioning as intended for the other recipients. After reviewing these, we often determine there is no true issue and mark them as “Fixed” or “Ignore,” but they continue to resurface under “Needs Review.”
This creates noise in our automation monitoring and makes it difficult to quickly identify legitimate issues.
We have attempted to design around this by adding logic to exclude certain users, but this becomes complex and not scalable. For example:
- We cannot easily build logic such as “if Project Manager is known AND not one of [specific users]”
- We also do not want to break the workflow entirely if a specific user is assigned and happens to have notifications turned off
- Since notifications are tied to multiple user properties in one action, excluding individuals becomes impractical
What we are looking for:
- A way for workflows to automatically skip or suppress notifications for users who have disabled workflow emails
- Or an option that prevents these scenarios from being flagged as “automation issues”
- Or guidance on best practices to handle multi-recipient notifications without generating repeated false-positive errors
Our goal is to keep our workflows clean and reliable, and currently these repeated alerts are creating unnecessary administrative distruption.