What Is a Trigger Conflict?
A trigger conflict happens when two or more flows share the exact same trigger definition. When a fan performs that action, ALL conflicting flows fire simultaneously — potentially sending the fan multiple messages at the same time.A Real Example
Imagine you have two launches running:- “Midnight Drive” Single Launch — Pre-Release flow with trigger: “Fan pre-saves your music”
- “Summer Vibes” Album Launch — Pre-Release flow with trigger: “Fan pre-saves your music”
How Fanaura Detects Conflicts
Fanaura continuously monitors all active triggers across your launches. When two or more flows share the same trigger definition, it flags them as a conflict. This detection happens:- In real time: As soon as you activate a flow with a conflicting trigger, the conflict count updates
- Across all launches: Conflicts are detected globally, not just within a single launch
- With specificity: Two flows both triggered by “Fan sends Instagram DM” with different keyword filters are NOT a conflict — the keywords make them distinct
Where Conflicts Appear
Active Triggers Overview
The primary place you will see conflicts is in the Active Triggers Overview on the Launches page. Look for:- Red conflict count badge: Shows the total number of trigger conflicts detected
- Conflict indicators on trigger groups: Groups with conflicts are highlighted
- “Conflicts Only” filter tab: Narrows the view to show only conflicting trigger groups
Flow Detail Page
When you open a flow that has a conflicting trigger, you may see a warning indicator near the trigger node on the canvas, alerting you that another flow shares this trigger.How to Resolve Conflicts
Here is the step-by-step process:Step 1: Open Active Triggers Overview
Navigate to the Launches page and find the Active Triggers Overview section.Step 2: Filter to Conflicts
Click the “Conflicts Only” filter tab. This hides all clean triggers and shows only the groups where two or more flows are competing.Step 3: Expand the Conflicting Trigger Group
Click on the trigger group (e.g., “Presave”) to expand it. You will see all the flows that share this trigger, each with its:- Flow name
- Launch name
- Cycle stage badge
- Inline toggle switch
Step 4: Decide Which Flows to Keep
Look at the competing flows and decide which ones should remain active:- Is one of these from a completed launch? Turn it off — it has served its purpose.
- Are both from active launches? Decide which campaign takes priority and disable the other.
- Are they targeting different audiences? Consider adding trigger filters (keyword matching, fan attributes) to make them distinct rather than disabling one entirely.
Step 5: Toggle Off Unnecessary Flows
Use the inline toggle switch to turn off the flows you do not want firing. This is instantaneous — the flow stops accepting new enrollments immediately.Step 6: Verify the Resolution
Switch back to the “All” filter tab and confirm:- The conflict count has decreased
- The trigger group no longer shows a conflict indicator
- Only the flows you want active are still toggled on
Types of Conflicts and How to Handle Them
Same Trigger, Different Launches
Scenario: A presave trigger is active in two different launches. Resolution: Turn off the presave trigger from the older launch. In most cases, you want fans to enter the newest campaign.Same Trigger, Same Launch, Different Stages
Scenario: Two flows within the same launch — one in Pre-Release and one in Release — both trigger on “Fan clicks streaming link.” Resolution: This might be intentional. The Pre-Release flow handles clicks before release day, and the Release flow handles clicks on release day. If your stage dates are set correctly, Fanaura will route fans to the correct flow based on the current stage. If not, disable the one that does not apply to the current phase.Same Trigger, Different Keywords
Scenario: Two Instagram DM flows both trigger on “Fan sends Instagram DM,” but one listens for “presave” and the other for “merch.” Resolution: This is NOT actually a conflict. Different keyword filters make these distinct triggers. Fanaura recognizes this and will not flag it.Truly Identical Triggers
Scenario: You accidentally created two flows with the exact same trigger and no distinguishing filters. Resolution: Decide which flow has the better content or is more current, and disable the other. If both are valuable, merge their actions into a single flow.Prevention Tips
The best way to handle conflicts is to prevent them in the first place:Before Activating Any Flow
- Open the Active Triggers Overview
- Search for the trigger type you are about to use
- Check if any other active flows already use it
- If they do, either disable the existing one or add filters to differentiate
When Creating New Launches
Ask yourself: “Are there triggers from my previous launches that are still active and might overlap with this new one?” If yes, go clean them up before activating new flows.Use Trigger Filters
Instead of broad triggers like “Fan sends Instagram DM,” use keyword-specific triggers like “Fan sends Instagram DM containing ‘PRESAVE’.” Filters reduce the chance of accidental overlap.Clean Up After Launches Complete
When a launch reaches its Post-Release phase and all fans have completed their flows, turn off the remaining triggers. A quick visit to the Active Triggers Overview after each campaign wraps up keeps your trigger list clean.The No-Conflict Zone
Triggers that fire for only one flow are in the no-conflict zone — safe to leave enabled without worry. You can view these by switching to the “No Conflicts” filter tab. If every trigger in your Active Triggers Overview is in the no-conflict zone, you will see a conflict count of zero. That is the goal.Tips and Best Practices
- Check for conflicts weekly: Even if you have not created new flows, other team members might have
- Resolve conflicts before they cause problems: Do not wait for a fan to report duplicate messages
- Use the “Conflicts Only” filter: It saves time by hiding all the clean triggers
- Document your trigger strategy: Keep a simple list of which triggers belong to which launch, especially if multiple people manage your Fanaura account
- When in doubt, use keyword filters: They are the simplest way to make similar triggers distinct