WorkerAttemptsExceededException

I’ve seen that sometimes not all Queued mails are sent and stay as Queued. Then in the next cron schedule, those queued jobs are marked as Fail.

Hey @frendeliko,

What does the top of the “Reports” tab in WP Offload SES look like?

Is the SES account out of sandbox mode and you’re keeping below the SES account’s rate limit and emails per 24hr limit?

Have you enabled debug.log and looked for any issues there?

–IJ

On top of the Reports tab I see an error:

There was an error attempting to retrieve your SES account details.

But the vast majority of the emails are getting sent without any problems. If this is the problem, how come can the service still be working?

The account is in production mode and we have a huge rate limit that is impossible to reach ??

Anyway, how do I enable the debug.log in the plugin?

Thanks for your time!!

• This reply was modified 1 year ago by Carlos Faria.

Hi @frendeliko,

Thanks for the response.

You can enable debug.log by editing your wp-config.php file on your server to replace this line –

define( 'WP_DEBUG', false );

With these lines –

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

This will cause all runtime errors, warnings, and notices to be written to /wp-content/debug.log, which will hopefully yield some better information about what’s going on.

More details about that at https://www.ads-software.com/support/article/editing-wp-config-php/#wp_debug

Once we have finished troubleshooting you should revert that config change and delete the debug.log file.

Oh! That log… Ok, I’ll activate that one and see if there are some errors…

I’ll come back if I get sth…

Thanks!!

So, this seems to be a problem with the IAM user that has restricted permissions to ses:ListEmailIdentities.

Can’t tell if this is for sure the fix, but it seems to. So I resolve the issue and I’ll post a new one if a new issue arises.

Thank you very much for your support.

Hi @carlos how did you track it to the IAM user and how did you fix?

In my case, setting up the defines allowed me to see the errors in the backedn.

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

I fixed it allowing the IAM User the permissions and pumping up the server RAM as it was causing some memory allocation problems.

Thanks, what did those errors in the debug.log show up under? I enabled and I am getting failed sends but can’t find any offload errors.

I got some errors like this one:

Allowed memory size of XXXXXXX bytes exhausted (tried to allocate XXXXXX bytes)

The ones about the user permissions appeared in the wp admin, in the SES settings section.