Flow debugging
If a flow does not run or emails do not arrive, check trigger, recipient, limits, and Mail Approval. This article walks through debugging step by step.
What you will see
Flow statistics show runs and success/failure.
Failed runs may show a reason (e.g. "No email address", "Limit reached").
Also verify the flow is On and the trigger table has recent rows.
How to set it up
1. Confirm the flow is On.
2. Check the trigger: new rows or changes in the chosen table? See Set up trigger.
3. Check recipient column: valid email on triggered rows?
4. Check limits: sending or flow limit reached? See Understand limits.
5. With Mail Approval: are emails waiting for approval? See Set up Mail Approval.
Tips
Test with one table row and your own email to validate the full chain.
Check statistics right after a test to see success or failure and why.
Common issues
Flow never runs: wrong trigger or flow Off. Check table and status.
Email missing but run succeeded: check spam, Mail Approval queue, and recipient address.
Failed "Limit reached": upgrade or wait for period reset; see Limits and Plans explained.
Failed "Recipient missing" or invalid email: fill the recipient column for those rows.
FAQ
Next step
Get started with a free account or view Pro.
Related articles
Understand flow statistics
Flow statistics: runs, succeeded, and failed. The flow dashboard in Feedback Analytics.
Set up trigger
Set a flow trigger: choose data table and event (new row or change). Step by step in Feedback Analytics.
Understand limits
Email and flow limits per plan and what to do when you hit a limit in Feedback Analytics.
Set up Mail Approval
Mail Approval: queue, approve, or auto-send. Pro feature in Feedback Analytics.