Email delivery troubleshooting: why aren't my emails sending?

If your emails aren’t sending, aren’t being delivered, or are failing outright, and it feels like email is broken inside the system, work through these causes in order. Depending on which email account you’ve connected, there are a few different reasons you might not be able to send email, but most cases come down to one of the causes below.

You’ve hit a sending limit

This is probably the most common reason, and it’s worth checking first if you can’t send email at all or notice sending has stopped completely.

If you’re still on a trial and haven’t verified your email address yet, you’re capped at 25 emails in total, not per day, in total. Every email counts toward that, a password reset, a welcome email, a test send, anything the system sends out on your behalf. Once those 25 are used up, sending simply stops.

To check, click the profile icon in the bottom left of your account and look for a message saying your account still needs verifying. If it’s there, follow the link to verify your email address, and the limit lifts straight away.

If you’re sending through the system mail, the platform’s own built in default sender, you’re capped at 250 emails a day instead. This exists to stop spam and abuse, and to protect deliverability for everyone else sharing the same sending infrastructure, not just you.

If you’re consistently running up against that 250 a day limit and genuinely need more, contact support. It can be raised on a per account basis once your sending history’s been reviewed and shows you’re not sending spam or abuse to anyone.

Authentication has broken

This is the other common cause behind a broken email connection, particularly where an account is connected through SMTP.

The usual story is that the password on the email account was changed somewhere outside the platform, and that change was never brought across into the connection settings here, so the account can no longer authenticate.

To fix it, go to Settings, then Connected Accounts. Find the email account in question, expand it, and open its settings. From there you can update the password, along with the port or host details if those have changed too, to make sure the connection actually matches what your email provider expects.

Finding out exactly why an email failed

If an email is failing, whether it went out through automations or through a connected provider like Microsoft, Google or SendGrid, the reason is recorded in the Automations History tab, the same place covered in the automations troubleshooting article.

You can check this from the main Automations page, where History shows failures across every automation, or from inside the specific automation where the email failed, which narrows things down and makes the actual error easier to find.

If the error message mentions authentication, it almost always comes back to the password, the port, or the hostname, something that meant the account simply couldn’t be reached. That points you straight back to the authentication fix above rather than anywhere else.