Why am I getting duplicate notifications?
Short answer
Duplicate notifications almost always come from overlapping workflows or the same trigger set up in two places, such as a personal alert and a team alert both firing on the same event. Check every active workflow touching that trigger before assuming it is a platform glitch.
Before you start
- An example of the exact notification that duplicated, with timestamps.
- Access to the workflows tied to that notification type.
- Access to personal and team notification settings.
- Knowledge of any recent workflow or integration changes.
Step by step
- 1
Confirm the notification is truly duplicated
Check timestamps and content to rule out two separate but similar events.
Two different events that look alike are not the same problem as one event firing twice.
- 2
Search for overlapping workflows
Look for more than one workflow listening for the same trigger event.
Two workflows built for the same purpose at different times is the most common cause.
- 3
Check personal and team notification settings separately
Confirm the same alert is not enabled at both the individual and team level.
Layered settings can each fire independently for the exact same event.
- 4
Review any connected integration for its own alerting
Some integrations send their own notification in addition to one built inside a workflow.
An external tool duplicating an internal alert is easy to miss if you only check one side.
- 5
Check for re-triggering caused by an edited record
See if a workflow re-fires when a field gets updated after the original trigger.
A trigger built too broadly can fire again on a minor edit to the same record.
- 6
Disable one source and test
Turn off the suspected duplicate source and reproduce the trigger to confirm only one alert arrives.
A controlled test proves the fix instead of just hoping the change worked.
- 7
Document which notification source is the official one
Note the intended single source so a well-meaning second setup does not get added later.
Duplicate notifications often return when someone recreates a fix that already exists.
What good looks like
- Each event triggers exactly one notification instead of several.
- The team trusts alerts again instead of tuning them out.
- Overlapping workflows and settings get identified and consolidated.
- A documented single source prevents the duplication from returning.
Common mistakes
The ways this goes wrong in support, and what to do instead.
Assuming it is a platform bug›
Time gets spent reporting an issue that is actually two workflows built for the same purpose.
Do this instead: Search for overlapping workflows and settings before assuming it is a system error.
Turning off notifications entirely to stop the noise›
Important alerts get missed because the whole notification type was disabled instead of fixed.
Do this instead: Identify and remove only the duplicate source, keeping the single correct one active.
Not checking team level settings›
A fix applied to one person's account does not stop the duplicate firing for the whole team.
Do this instead: Check both personal and team notification settings for the same overlapping trigger.
Frequently asked
6 questions about fix duplicate notificationsRelated guides
Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.
Do this next
The natural follow-on tasks once this one is working.
More in Support
Nearby tasks that share the same setup and vocabulary.
Was this guide helpful?
Tell us what worked and what didn't. It shapes what we rewrite next.
You didn't get into business to be in the tech business.
Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.