You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The emails from queue could be sent multiple times to the same contact if there is an exception thrown during the batch processing.
How can we reproduce this issue?
Set the Frequency rule in the Mautic settings to 1 message per day.
Create a segment with some contacts, one contact should have an empty first name (null in the database) and at least one company.
Create and send an email to the segment, add the {contactfield=firstname} to the email content
Clone the email and send it again - it should be added to the message queue because of the limit.
After 24 hours, run the command to send the queue ddev exec php bin/console mautic:messages:send.
The error should be thrown while executing this command.
Batch emails are dispatched and the queue table entries are modified only after the successful sending of all emails. In the event of an error during the batch process, the queue remains unaltered even though certain emails may have been sent.
Comments on closed issues are hard for our team to see.
If this issue is continuing with the lastest stable version of Mautic, please open a new issue that references this one.
Mautic Version
5.0.x series
PHP version
8.0
What browsers are you seeing the problem on?
Not relevant
What happened?
The emails from queue could be sent multiple times to the same contact if there is an exception thrown during the batch processing.
How can we reproduce this issue?
{contactfield=firstname}
to the email contentddev exec php bin/console mautic:messages:send
.Batch emails are dispatched and the queue table entries are modified only after the successful sending of all emails. In the event of an error during the batch process, the queue remains unaltered even though certain emails may have been sent.
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: