ERROR - execution expired (email)

Product Support

AI-generated summary

Mako encountered an ERROR - execution expired (email) issue while trying to send a test email in their Discourse admin dashboard. Despite checking their app.yml settings and rebuilding several times, the issue persisted. Jahan Gagan suggested checking the error logs in /sidekiq, which Mako did, but was unsure how to interpret them. However, Mako eventually discovered that the issue was due to Digital Ocean blocking port 587, which is the default port suggested by Brevo for SMTP email. By switching to port 2525 in their app.yml settings, Mako was able to resolve the issue and successfully send a test email.

1

In /admin I see this prompt for the first time:

There are 91 email jobs that failed. Check your app.yml and ensure that the mail server settings are correct. See the failed jobs in Sidekiq.

I sent a test email, and I was greeted with:

ERROR - execution expired (email)

I am using Brevo for SMTP email.

I went ahead and double checked my app.yml to ensure that my settings were correct, and they are. I have rebuilt a few times now, and even shut off the server and turned it back on. Nothing is fixing it.

I have no unofficial plugins installed.

3

Checkout /sidekiq in your Discourse admin dashboard and inspect the error logs.

4

I am unsure what to make of these logs:

image
image1920×2790 393 KB

5

Located the issue:

I utilize Digital Ocean for an Ubuntu Server, and Brevo for SMTP email. Digital Ocean blocks port 587, which by default, Brevo suggests. However, Brevo allows you to use port 2525, which is not blocked by Digital Ocean.

I changed the port in my app.yml and rebuilt. I was then able to send an email test, and no longer had email jobs that failed.

Source