Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.fanaura.com/llms.txt

Use this file to discover all available pages before exploring further.

Every flow in Fanaura has a simple on/off switch — the is_active toggle. When it is on, the flow is live and executing. When it is off, it is dormant. Understanding exactly what happens when you flip that switch is important for managing your automations without disrupting fan experiences.

​
The is_active Toggle

The toggle is a simple switch with two states:
  • The flow’s trigger is listening for events
  • New fans are being enrolled
  • Actions are executing for enrolled fans
Toggling a flow off does NOT stop fans who are already in it. It only prevents new fans from entering. Existing fans continue receiving messages and progressing through the flow until they complete it.

​
Where to Toggle

You can toggle a flow on or off from three different places in Fanaura:

Flow Detail Page

Open the flow in the Flow Builder. The is_active toggle is in the top-right corner. Most common location.

Active Triggers Overview

Navigate to Launches and find the Active Triggers Overview. Each trigger row has an inline toggle. Best for managing multiple flows.

Launch Detail Page

Open a launch and look at the flow cards under each cycle stage. Each card includes a toggle indicator.

​
What Happens When You Toggle ON

When you activate a flow:
1

Trigger Starts Listening

Whatever event your trigger is configured for (presave, DM keyword, email open, etc.) is now being monitored in real time.
2

New Enrollments Begin

Any fan who performs the trigger action from this moment forward will be enrolled in the flow.
3

Actions Start Executing

Enrolled fans begin moving through the sequence — delays start counting, emails start sending, conditions start evaluating.
4

Flow Appears in Active Triggers

Your trigger is now visible in the global Active Triggers Overview dashboard.

​
First Activation Checklist

Before toggling a flow on for the first time, verify every item in this checklist to avoid sending broken or incomplete messages to fans.
  • All nodes are configured (no empty actions or unconfigured conditions)
  • Email content is finalized and test emails have been sent
  • SMS messages are reviewed and tested
  • Conditions are correctly configured with the right criteria
  • Delays are set to appropriate durations
  • Flow Settings are reviewed (timezone, time windows, re-entry, etc.)
  • Active Triggers Overview checked for conflicts
  • You have triggered the flow yourself for an end-to-end test (if possible)

​
What Happens When You Toggle OFF

When you deactivate a flow:
1

Trigger Stops Listening

No new events are captured. If a fan presaves right now, the flow will NOT enroll them.
2

No New Enrollments

The total enrolled count stops growing. No new fans enter.
3

Existing Fans Continue

Fans already in the flow keep moving. Their delays keep counting, their scheduled actions keep firing, and their conditions keep evaluating. They will complete the flow as designed.
4

Flow Disappears from Active Triggers

The trigger is no longer listed in the Active Triggers Overview since it is not active.

​
Why Existing Fans Continue

This design is intentional. Imagine a fan is halfway through a 7-day email drip sequence and you toggle the flow off. It would be a terrible experience if they suddenly stopped receiving the sequence mid-journey. Fanaura lets them finish what they started.
If you genuinely need to stop all execution for all fans (including those already in progress), you would need to delete the flow entirely. But in nearly all cases, letting existing fans complete is the right behavior.

​
When to Toggle OFF

Your launch has completed and you no longer need the flow. Turn it off so it does not keep enrolling fans from stale triggers.
If you need to significantly edit an active flow (restructuring nodes, changing conditions, modifying the trigger), it is safer to:
  1. Toggle off
  2. Make your edits
  3. Test the changes
  4. Toggle back on
This prevents fans from entering a half-edited flow.
The Active Triggers Overview shows that this flow conflicts with another flow’s trigger. Turn one off to prevent duplicate messages.
Something is going wrong — fans are receiving the wrong messages, conditions are misbehaving, or errors are piling up in the execution logs. Toggle off to stop the bleeding while you investigate.
A flow that runs during a specific period (holiday merch campaign, summer tour promotion) should be turned off when the season ends. You can always turn it back on next time.

​
When to Toggle ON

You have built the flow, configured the settings, tested the messages, and checked for conflicts. It is go time.
A seasonal flow is ready to run again. Toggle it on and the trigger starts listening immediately.
Your launch moves from Pre-Release to Release. Toggle on the Release-stage flows and consider toggling off Pre-Release flows that are no longer relevant.

​
Impact on Other Flows

Toggling a flow on or off only affects that specific flow. Other flows are completely unaffected, even if they share the same trigger type.
Turning off one presave flow does NOT affect another presave flow. Turning off all flows in one launch does NOT affect flows in other launches. The toggle is flow-specific, not trigger-specific or launch-specific.

​
Go-to-Flow Interactions

If Flow A has a Go-to-Flow action that redirects fans to Flow B:
Fans redirect successfully and enter Flow B as expected.
If you are deactivating a flow that other flows redirect to, check whether any active flows use Go-to-Flow pointing at it. You may need to update those references.

​
Quick Automations Toggle

Quick Automations (standalone flows not tied to a launch) work the same way. They have their own is_active toggle in the Automations tab on the Launches page. Toggle behavior is identical — on means active, off means no new enrollments but existing fans continue.

​
Best Practices

  • Check Active Triggers Overview: Prevent conflicts by verifying no other flow uses the same trigger
  • Send test messages: Email, SMS, and DM content should be verified before fans see it
  • Review Flow Settings: Timezone, time windows, and enrollment rules are configured correctly
  • Start with one flow: If your launch has multiple flows, activate them one at a time and verify each is working before activating the next

​
The Golden Rule

When in doubt, toggle off rather than delete. Toggling off is completely reversible — you can toggle back on at any time with no data loss. Deleting a flow is a much bigger action (even with the 30-day recovery window). Toggle off first, investigate, and only delete if you are certain the flow is no longer needed.

​
What Happens Next

You now have a complete understanding of the Fanaura Flow Builder — from creating flows and configuring triggers to building branching logic, personalizing messages, managing settings, monitoring enrollment, debugging with logs, and controlling activation. Go build something amazing for your fans.