Flows FAQ

There's no hard limit on the number of flows you can create. Most users run dozens of flows without any issues. However, if you're planning to create an exceptionally large number of flows or very complex flows with many entry points, it's worth reaching out to our team first - we can help optimize your setup for the best performance.

Flows run completely automatically once published. When the trigger event happens and any conditions are met, the flow executes its actions without any manual intervention.

You can use the preview feature in the flow editor to review your flow logic and make sure everything looks right before publishing. However, there's no way to test the flow with real data before it goes live - you'll need to publish it to see it in action.

All flows with matching triggers will run independently. For example, if you have two flows that both trigger on "customer installs app", both will execute when someone installs your app.

Yes! If your flow has multiple entry points (different triggers), a customer can go through all of them without any special settings. Each entry point works independently. However, if you want a customer to re-trigger the same entry point multiple times, you need to enable "Allow customers to re-enter this flow" in your flow settings.

Yes, you can unpublish a flow at any time to stop it from running. Your flow will remain saved and you can republish it whenever you're ready.

Check these common issues:
• Make sure your flow is published
• Verify the trigger event is actually happening (check your app's activity)
• Review any conditions - they might be too restrictive
• For usage event triggers, ensure the events are being sent correctly to Mantle
• Check if the customer meets all the specified conditions

Yes! You can add multiple conditions to make your flows more specific. All conditions must be met for the flow to run. For example, you could trigger on "customer installs app" AND "customer has tag 'VIP'" AND "customer is not on trial".

You can't start a flow purely based on time - every flow needs a trigger event to anchor the timing. However, you can add wait/delay actions after a trigger to create time-based sequences. For example: trigger on install, wait 7 days, then check if still active.

Yes, flows will trigger for test customers unless you specifically add a condition to exclude them. You can add "Test customer is false" as a condition to prevent flows from running on test accounts.

No, email actions require valid customer email addresses. If you haven't set up email collection yet, check out our email setup guide to learn how to import customer emails or set up automatic collection through Mantle Email.

Check the flow activity log to see exactly what happened. For email actions specifically, common issues include:
• Customer has no email address
• Email template has errors or missing content
• Email isn't configured to send to the right contact list
• Issues in the email editor (broken links, missing images, etc.)

Other common failures:
• Slack actions failed because integration isn't properly configured
• HTTP requests failed due to incorrect URLs or authentication

The activity log will show you the specific error for each failed action.

Yes! Each flow has an activity log that shows every time it's triggered, which actions succeeded or failed, and any error messages. This is great for debugging and monitoring your automations.

Add more specific conditions to narrow down when the flow runs. You can also use custom fields to track flow states - for example, set a field when the flow runs and add a condition to check if it's already been set.

Yes, you can edit published flows at any time. Changes take effect immediately, so be careful when editing active flows. Consider testing changes in a duplicate flow first if you're making major modifications.

The flow will run each time the trigger event happens, unless you've added conditions to prevent it. For example, if your flow triggers on "customer installs app" and they uninstall/reinstall, the flow will run again on the second install.