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.

When something goes wrong — or when you want to make sure everything is going right — the Execution Logs tab is where you go. It shows every single action that has executed for every fan in this flow, with timestamps, statuses, and error details. Think of it as the flight recorder for your automation. If a fan says “I never got that email” or a flow seems to be stalling, the execution logs tell you exactly what happened and why.

​
Where to Find It

Open any flow in the Flow Builder and click the “Execution Logs” tab at the top of the page.

​
What the Logs Show

The Execution Logs tab displays a chronological list of every action that has fired in this flow. Each log entry contains:

​
Fan Name and Email

Who the action was executed for. Click the fan name to open their full profile.

​
Action Type

What kind of action was executed:

Email

A Send Email action fired.

SMS

A Send SMS action fired.

Instagram DM

A Send Instagram DM action fired.

Delay

A delay completed.

Condition

A condition was evaluated.

Tag/Update

A fan profile was updated.

Add to List

A fan was added to a list.

Invite to Extra

A fan was invited to an Extra.

Go to Flow

A fan was redirected to another flow.

​
Timestamp

The exact date and time the action executed, displayed in your account timezone. Hover for the full timestamp with seconds.

​
Status

Every log entry has one of three statuses:
The action executed correctly. The email was delivered, the SMS was sent, the condition was evaluated, the delay completed. Everything worked as expected.
The action encountered an error and did not complete. The log entry includes an error message explaining what went wrong. Common error messages include:
  • “SMS delivery failed: Fan does not have SMS opt-in” — The fan has not opted in to SMS
  • “Instagram DM failed: 24-hour messaging window expired” — The fan’s last interaction was more than 24 hours ago
  • “Email delivery failed: Email address bounced” — The fan’s email address is invalid
  • “Email delivery failed: Unsubscribed” — The fan unsubscribed from emails
  • “Condition evaluation failed: Missing fan data” — The condition references a fan attribute that does not exist
  • “Go-to-Flow failed: Target flow not found” — The target flow was deleted or deactivated
  • “SMS delivery failed: No provisioned phone number” — Your account does not have an SMS number provisioned
The action is scheduled but has not executed yet. This typically appears for delayed actions that are queued for future delivery.

​
Details

Each log entry includes contextual details specific to the action type:
Action TypeDetails Shown
EmailSubject line of the email sent
SMSThe text message content
Instagram DMThe DM message content
DelayDuration and whether it completed naturally or timed out
ConditionThe condition evaluated and the result (Yes or No)
Tag/UpdateWhich tag was added/removed or field updated
Go to FlowWhich flow the fan was redirected to
Use the search bar to filter logs by:
  • Fan name: Find all actions executed for a specific fan
  • Fan email: Search by email address
  • Action type: Type “email,” “sms,” “condition,” etc. to filter by action type
Search is incredibly useful when you are investigating a specific fan’s experience or looking for all failures of a particular type.

​
Filters

Narrow the logs to show only specific action types:
  • All: Every action (default)
  • Email: Only Send Email actions
  • SMS: Only Send SMS actions
  • Instagram DM: Only Send Instagram DM actions
  • Delay: Only completed delays
  • Condition: Only condition evaluations
  • Tag/Update: Only profile updates
  • Go to Flow: Only flow redirections

​
Expandable Entries

Click any log entry to expand it and see the complete execution history for that specific fan — every action in chronological order, not just the one you clicked. The expanded view shows the fan’s full journey through the flow:
  1. Trigger event and enrollment timestamp
  2. Every delay, action, and condition in order
  3. Which branch the fan took at each condition
  4. Success/failure status for each step
  5. Error messages for any failed steps
This is the single most useful debugging view in Fanaura. Instead of piecing together what happened from individual log entries, you see the entire story in one place.

​
Debugging Common Issues

  1. Search for the fan by name or email
  2. Find the Send Email log entry
  3. Check the status:
    • Success: The email was sent. Check the fan’s spam folder or confirm their email address is correct.
    • Failed: Read the error message. Common causes: email bounced, fan unsubscribed.
    • Not found: The fan may not have reached the email action yet. Expand their row to see where they are in the flow.
  1. Filter by action type: Delay
  2. Look for delays with unusually long durations
  3. Check if fans are stuck on fan-action delays waiting for an action they are unlikely to take
  4. Consider adjusting the timeout duration on those delays
  1. Filter by action type: Condition
  2. Look at the condition results (Yes/No) for multiple fans
  3. If most fans are going down the wrong branch, the condition logic may be misconfigured
  4. Click a specific condition entry to see what data was evaluated
  1. Filter by action type: SMS
  2. Filter by status: Look for failed entries
  3. Common causes:
    • No SMS opt-in: The fan has not opted in. This is the most common cause.
    • Invalid phone number: The fan’s phone number is missing or malformed.
    • No provisioned number: Your SMS number is not set up or has been disconnected.
    • Rate limit: If you are using a local number (2 msg/min), messages may be queued and delayed.
  1. Filter by action type: Instagram DM
  2. Read the error messages:
    • “24-hour messaging window expired”: The fan’s last interaction was too long ago. Shorten delays before IG DM actions.
    • “Fan Instagram handle not found”: Fanaura does not have the fan’s Instagram username.
    • “Instagram API rate limit”: Too many DMs sent too quickly. This resolves on its own.
  1. Search for the condition in the logs
  2. Expand several fan entries to see what data the condition evaluated
  3. Common causes:
    • The fan attribute being checked does not exist for most fans
    • The comparison value is wrong (e.g., checking for “gold” when the actual value is “Gold” — case sensitivity)
    • The condition checks behavior from a previous flow that fans have not been through

​
Log Retention

Execution logs are retained for the lifetime of the flow. As long as the flow exists, its logs are available. Deleted flows (in the 30-day recovery window) retain their logs until permanent deletion.
For very active flows with thousands of fans, the date range filter and search tools keep the logs manageable.

​
Tips and Best Practices

After activating a flow, review the execution logs to make sure the first batch of fans is processing correctly.
When investigating issues, start with failed actions — they have the error messages you need.
Individual log entries are useful, but the expanded per-fan view tells the complete story.
If a fan should have received 3 emails but the logs show only 1, something went wrong between actions 1 and 3.
If you notice patterns in failures, document them and adjust your flow logic accordingly.
If you edit an active flow, check the logs afterward to make sure the changes did not break anything for fans already in progress.

​
What Happens Next

The final piece of the Flow Builder puzzle is understanding how to toggle flows on and off safely. Head to Toggling Flows.