Thread Starter
dimal
(@dimalifragis)
I mean the next GD queue run time is behind the current time ….. whatever that means for the execution ….
Hi,
WordPress cron is really a pseudo cron, it doesn’t really run at the exact time it should, something has to trigger it (loading of any page does it), so actual execution of the cron can be delayed until the trigger happens. If you need cron to be run on the exact time, you should set up server-based cron that will trigger WordPress cron. I do that for all my websites.
The cron from my plugin has it run after you visited the page? If it has, that proves the cron delay until the trigger. If it hasn’t, then, you have some other cron related issue on your website.
Milan
Thread Starter
dimal
(@dimalifragis)
I don’t use internal CRON but a 5 minutes Cpanel CRON.
I will have to test more this, since it seems that i also get double or triple emails (same email).
Thank you
When plugin processes queue, it reads the emails and immediately marks them as in processing to avoid duplicate sending. If you get duplicated emails, something is wrong with your cron, and it is possible that cron is fired more than once at the same time so that two processes manage to get the data before the emails are marked as in processing.
WordPress cron has protection for this case that works really well, and I never had an issue with it. You should monitor how often the cron is firing and is their instances of firing multiple times at the same time.
Thread Starter
dimal
(@dimalifragis)
Well i route to your plugin all emails from stock WP (no dups), i route emails from wpForo forum plugin (no dups). But all dups seems to come from a specific plugin.
I will have to closely look at this, most probably nothing to do with your plugin, since disabling GD Queue doesn’t seem to solve the problem.
Many thanks for the explanations.
Thread Starter
dimal
(@dimalifragis)
I’m posting more information, just in case someone searches in the future about STUCK Crons in WordPress.
It appears that maybe ALL WordPress plugins that disable WP Updates somehow make CRONS stuck for a while.
At least all 4 i tried showed the very same problem. So if you use any WordPress plugin to Disable Updates, check your CRONS if stuck (and you do not know it, as i did). With CRONTROL plugin. If you see some job stuck showing (NOW) for more that a few seconds, then you know you have a problem.
