The scheduled task selects 250 users that have not received the list for a week (or whatever you changed the interval to), ordered by User ID in ascending order.How does the scheduled task know where to start if it's been disabled for a while and then is enabled again?
The query I posted above is the method for that.Is there a way to reset the marker for the scheduled task back to #1?
Ah yeah, I didn't think to mention that - this mod uses vBulletin's mail queue system, so if your forum has low activity (so the scheduled task doesn't get processed often) or the mails per cron run is set very low (I think by default it's set at 10), then that could be a cause for delay.Okay. Thank you. I guess I need to look elsewhere for the "bottleneck", e.g., vBulletin mail settings.
SELECT * FROM user
WHERE dbtech_newsletter_receive = 1
AND dbtech_newsletter_lastreceive <= (1461974400 - (dbtech_newsletter_frequency * 604800))
ORDER BY userid ASC
LIMIT 250
UPDATE user SET dbtech_newsletter_lastreceive = 0
UPDATE user SET dbtech_newsletter_lastreceive = 0
#1054 - Unknown column 'dbtech_newsletter_lastreceive' in 'field list'
Can you check your vBulletin Options under Email Options that the "mail per scheduled task run" is set to a respectable amount (default is 10 I believe, I recommend 250)?All of the forums using the Pro version are now showing signs of "slippage", with the newsletter showing up on days that gradually slide toward the weekend and then into the next week.
Did you remember to include your table prefix?Any suggestions?
Can you check your vBulletin Options under Email Options that the "mail per scheduled task run" is set to a respectable amount (default is 10 I believe, I recommend 250)?
This is the most common reason for this. You can check if this is the case by checking if the mailqueue table is full.
Did you remember to include your table prefix?
We use essential cookies to make this site work, and optional cookies to enhance your experience.