-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
40 emails stuck as "queued" #24
Comments
Did you manage to fix this @dzg ? I found that the cron job to send the emails was not firing correctly so i disabled then re-enabled the plugin. Seems to work so far 🤞 |
Don't know if is the same problem, but here happened that for about 8hrs every mail sent was put on queue for a long time (stuck?) and then failed. This is the second time this happens. Looking on db, the error is "DeliciousBrains\WP_Offload_SES\WP_Queue\Exceptions\WorkerAttemptsExceededException" so every attempt (3 for each mail) is failing. But there is no log to understand why. It could be in some way related to the environment being multi-server (multiple instances behind a load balancer, common DB). |
Another cause might be if your website is behind a htpasswd, for a staging website or similar. |
Mh it's not my case.
…On Tue, 16 Mar 2021 at 11:04, Dan Lawson ***@***.***> wrote:
Another cause might be if your website is behind a htpasswd, for a staging
website or similar.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADI3A2XO2M4FQPLKN7N2V3TD4UKJANCNFSM4XJRR5VA>
.
|
Same issue for me, its the 3rd time this month. Emails got stuck for about 10-30 min, then got sent. Also Our server has auto scaling with at least 2 instances running behind a load balancer with common filesistem and DB. Right now is not a critial error but is weird to recieve some emails and not others, in the future when users can manage their own account, this error will be fatal, if not fixed, we will have to move to another plugin |
A solution seems to be disabling automatic WP cron, and setting up a
crontab pinging /wp-cron.php every 30-60s.
…On Wed, 28 Apr 2021, 22:21 Juan Viera, ***@***.***> wrote:
Same issue for me, its the 3rd time this month. Emails got stuck for about
10-30 min, then got sent. Also Our server has auto scaling with at least 2
instances running behind a load balancer with common filesistem and DB.
Right now is not a critial error but is weird to recieve some emails and
not others, in the future when users can manage their own account, this
error will be fatal, if not fixed, we will have to move to another plugin
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADI3A7LPUVTAWRGVT4P5ETTLBU3ZANCNFSM4XJRR5VA>
.
|
This morning we sent 370 emails, and in the Activity tab all are "Sent" except for 40 which seems to be stuck in a "Queued" state.
Why would this happen? SES console shows that everything is peachy.
Sending a test email works fine.
The text was updated successfully, but these errors were encountered: