Double email notifications

Hi. I was just about to create a new topic when I saw this topic created by @kacsalla . We have been using the Notifications plugin on wealthtender.com for over a year, but continue to have problems with multiple notifications being sent, often 3x.

Also, we have already tried the troubleshooting recommended on your site for background processing, but this doesn’t seem to be helping the issue.

We are eager to find a solution and appreciate your help.

– Brian

Thank you both for the report!

@kacsalla would you be able to follow those steps and let us know if it helped you?

@wealthtender can you let me know which Trigger and WordPress editor are you using?

@kubitomakita thanks for your answer. switching to wp cron solved my problem!

Hi @kubitomakita Thanks for your follow up. To answer your question, the triggers where we have seen this issue occur include – 1) Comment Approved, 2) Post Published.We are currently on WordPress version 5.8.3. Thank you.

@wealthtender we’re investigating this currently with another WordPress instance. Will keep you updated.

Hi @kubitomakita . Thank you very much for the update. Will stand by. Brian

Hi @kubitomakita . After not experiencing issues for almost two weeks, today when I published a post, the notification to two email addresses resulted in the notification being sent EIGHT TIMES to each email address.

Five minutes later when I published a different post, the notification worked correctly.

Have you identified any issues to resolve this from occurring? Unfortunately, we’re beginning to look for alternatives to your plugin to remedy the issue, but would prefer to not change plugins if you can troubleshoot and resolve this for us.

Thank you.

Hi, this is extremely hard to track down, especially when the outcome is not the same each time you test. The issue we had in the other instance was specific to the set of plugins used there and while we’ve been able to create a fixed plugin for it, we didn’t really find out the original cause.

We’re still keeping an eye on the issue, but without access to the exact WordPress instance where the issue occurs, it might be impossible to get it fixed.