Skip to main content
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:
  • On (Active): The flow’s trigger is listening for events, new fans are being enrolled, and actions are executing for enrolled fans
  • Off (Inactive): The trigger stops listening, no new fans are enrolled, but fans already in the flow continue their journey
That last point is crucial and worth repeating: toggling a flow off does NOT stop fans who are already in it. It only prevents new fans from entering.

Where to Toggle

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

1. Flow Detail Page

Open the flow in the Flow Builder. In the top-right corner of the page, you will find the is_active toggle. Click it to switch between on and off. This is the most common place to toggle — you are already in the flow, reviewing the canvas and settings, and the toggle is right there.

2. Active Triggers Overview

Navigate to the Launches page and find the Active Triggers Overview section. Each trigger row has an inline toggle switch that controls the associated flow. This is the best place to toggle when you are managing multiple flows across multiple launches. You can see all your active triggers at a glance and turn individual flows on or off without navigating into each one.

3. Launch Detail Page

Open a launch and look at the flow cards under each cycle stage. Each flow card includes a small toggle indicator. Click the flow card to access its toggle. This is convenient when you are reviewing a specific launch and want to quickly manage which flows are active for each stage.

What Happens When You Toggle ON

When you activate a flow:
  1. The 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. The flow appears in Active Triggers Overview: Your trigger is now visible in the global trigger dashboard

First Activation Checklist

Before toggling a flow on for the first time:
  • 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. The 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. The flow disappears from Active Triggers Overview: The trigger is no longer listed 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

The Campaign Is Over

Your launch has completed and you no longer need the flow. Turn it off so it does not keep enrolling fans from stale triggers.

You Need to Make Changes

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.

A Conflict Was Detected

The Active Triggers Overview shows that this flow conflicts with another flow’s trigger. Turn one off to prevent duplicate messages.

Debugging an Issue

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.

Seasonal Pause

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

Everything Is Ready

You have built the flow, configured the settings, tested the messages, and checked for conflicts. It is go time.

Reactivating After a Pause

A seasonal flow is ready to run again. Toggle it on and the trigger starts listening immediately.

A New Stage Begins

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. This means:
  • 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:
  • Flow B is active: Fans redirect successfully and enter Flow B
  • Flow B is inactive: The Go-to-Flow action will still attempt to redirect. Whether the fan enters depends on Flow B’s enrollment settings. In most cases, the redirect succeeds because Go-to-Flow bypasses the trigger requirement — it is a direct enrollment.
Tip: 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

Before Toggling ON

  • 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

After Toggling ON

  • Monitor Execution Logs: Check within the first hour for any failed actions or unexpected behavior
  • Check Enrollment: Verify fans are entering and progressing through the flow
  • Watch for conflicts: If the Active Triggers Overview shows a new conflict, resolve it quickly

Before Toggling OFF

  • Check Active count: How many fans are currently in the flow? They will continue to completion, so be aware of any time-sensitive actions remaining in their journey.
  • Notify your team: If other people manage your Fanaura account, let them know you are deactivating a flow
  • Document why: Add a note to the flow description explaining why it was deactivated and when/if it should be reactivated

After Toggling OFF

  • Verify in Active Triggers Overview: The flow’s trigger should no longer appear in the active list
  • Check for Go-to-Flow references: Make sure no active flows are trying to redirect fans to this deactivated flow
  • Monitor existing enrollments: Fans in progress will continue — keep an eye on execution logs for a few days to ensure they finish smoothly

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.