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
We came in a situation w here the our queue was not running. After a few hours we've seen this and started the queue. Immediately the queue was being cleared. From so far, everything looked fine until we saw that Mailator dispatched the same mail everytime.
The problem
The problem here lies that the scheduler from mailator see that the mail has not yet been sent and disptaches a new job onto the queue. Normally this is no problem but when the job is STILL on the queue, this is a problem. In our situation we had a few customers receiving more than 100 mails.
This is a serious problem for us because it can happen in the future that the scheduler is running but the queue is not, how can we avoid this problem, does the author have an idea?
The text was updated successfully, but these errors were encountered:
Context
We came in a situation w here the our queue was not running. After a few hours we've seen this and started the queue. Immediately the queue was being cleared. From so far, everything looked fine until we saw that Mailator dispatched the same mail everytime.
The problem
The problem here lies that the scheduler from mailator see that the mail has not yet been sent and disptaches a new job onto the queue. Normally this is no problem but when the job is STILL on the queue, this is a problem. In our situation we had a few customers receiving more than 100 mails.
This is a serious problem for us because it can happen in the future that the scheduler is running but the queue is not, how can we avoid this problem, does the author have an idea?
The text was updated successfully, but these errors were encountered: