Emails aren't being sent

An email that does not arrive fails in one of three places: the Send email step never ran, the step ran and failed, or the message left Beezr and went missing on the way. Start by opening the workflow’s Runs. If the Send email step shows a failure, the message tells you why. If it shows success, go to the last section.

No mail sender is set up

Check. The email step needs a sender. Open Account settings › Mail Setup. You need a mail server and a mail client (the sender address). In the step, From and to names the sender. A run that fails with a message about missing mail configuration points here.

Fix. Add a server, add a sender, and pick it in the step. Or choose Beezr Notifications, the built-in sender, in the step.

The server settings are wrong

Check. In Mail Setup, click Check next to the server. Check connects and signs in. Use Send test to deliver a message and check delivery. The result names the stage that failed:

Result	Meaning	What to do
Can’t connect	The server did not answer on that port	Check the host name. Ask IT whether outbound traffic on the port is blocked
Encryption mismatch	The port and the encryption disagree	Port 465 expects SSL/TLS from the start. Port 587 uses STARTTLS. Use the Switch to SSL/TLS suggestion if it is offered
Sign-in failed	The username or password was rejected	See the provider notes below

Provider notes the page itself shows:

• Microsoft 365: sign in with the mailbox address and its password. Authenticated SMTP must be allowed for that mailbox in the Microsoft 365 admin center.
• Google Workspace: use an app password, not the normal password.
• Amazon SES: use the SES SMTP credentials, not AWS keys. The sender address must be verified.
• SendGrid: the username is the word apikey, and the password is your API key. The sender must be a verified sender.

Fix. Correct the setting, Check again, then Send test to your own address.

Tip from a Beezr Consultant

If the password is right and sign-in still fails, ask the mailbox owner or IT to allow password sign-in for that mailbox with the provider.

The step has no recipients

Check. In To, CC and BCC, the values are evaluated when the step runs. If all of them come out empty, the step fails. This happens when you insert a field that was empty on the record, or a list that was empty.

Fix. Make sure the field has a value, or add a fallback address in To. Add a Decision before the step that checks the field.

An attachment or the Beezr sender gets in the way

Check. Beezr Notifications is the simple built-in sender, for messages without attachments or BCC. An attachment comes from a file field, or from the file a Smart document step made.

Fix. For messages with attachments or BCC, choose your own mail sender in From and to. In Attachments, Add a file field, or insert the file that the Smart document step produced.

The message template has a missing value

Check. When the message uses a table that repeats over a list, the message is a template. A value that does not exist in the list makes the step fail with a template error.

Fix. Pick the list again with Choose the data to show, and use only fields that list has.

The step ran but nobody got the email

Check. If the run is Completed and the Send email step shows no error, the server accepted the message. Look in the recipient’s spam folder. Check that the sender address is allowed to send from your domain. Providers such as SES and SendGrid also require the sender to be verified.

Fix. Send a Send test to a mailbox you control and compare. If that arrives and the workflow’s does not, check the From sender and the addresses the step builds from your data.