Skip to main content
A flow showing a successful run only confirms that Parabola handed the email off for delivery — it doesn’t guarantee the message reached the recipient’s inbox. Delivery itself happens through Parabola’s outbound email provider, and can fail or get delayed after the step reports success.

​
Checklist

1

Check the recipient's spam or junk folder

Ask the recipient to check spam/junk first — this is the most common cause and resolves the majority of “missing email” reports.
2

Verify the recipient address

Open the step’s run history and confirm the email address(es) used for that run are correct and don’t contain typos, extra whitespace, or merge-tag errors (for Send emails by row, a bad column value can silently point at the wrong address).
3

Check the step's run history for errors

Open the flow’s run history and inspect the email step’s output for that run. A “success” status on the step means the request to send was accepted — it does not confirm the receiving mail server accepted the message.
4

Rule out a sender/reply-to misconfiguration

Confirm the Reply-to address (if set) is valid. A malformed Reply-to can cause some receiving mail servers to bounce the message even though Parabola’s send succeeded.
5

Contact support with your run ID

If the above don’t explain it, email help@parabola.io or use the in-app chat with your flow name, run ID, and approximate send time. Support can check Parabola’s outbound delivery and bounce logs, which aren’t visible from the flow itself.

​
Common causes

  • Spam filtering — the most frequent cause. The email sent successfully but the receiving server or client routed it to spam/junk.
  • Recipient server rejected or bounced the message — some corporate mail servers reject messages from unrecognized senders or apply strict spam scoring.
  • Malformed recipient address — a typo, blank cell, or bad merge-tag value produced an invalid “to” address.
  • Platform-wide sending issue — Parabola sends all outbound flow emails through SendGrid. If SendGrid or Parabola’s sending pipeline has an incident, it affects all users simultaneously — see below.

​
If this looks like a platform-wide issue

If you notice multiple flows or scheduled sends failing to deliver around the same time, especially after a change in behavior from a feature that was previously working, this may be a broader delivery incident rather than a flow-specific issue. Report it to help@parabola.io with your run ID either way — even during an incident, support needs specific run IDs to confirm which sends were affected.
Last modified on July 14, 2026