Missing scheduled posts

I’m afraid Jetpack might not help you solve this issue.

Scheduling problems usually have 2 main causes:

1. You might not have any readers that come and visit your website, thus triggering WordPress’ scheduling system. This can be solved by making sure you have regular visits on your site. Tools like Jetpack’s Monitor module, that have a bot visiting your site every 5 minutes, would solve that issue.
2. If you have visitors, but WordPress’ scheduling system still doesn’t work well, you’ll need to contact GoDaddy again, and ask them if they make any changes to the way Cron works on your WordPress installation. They can also check your site’s logs to make sure calls to the wp-cron.php file happen regularly.

I hope this helps!

Jeremy – you said “I’m afraid Jetpack might not help you solve this issue”, but then recommended JEtpack Notifications? ??

So does Jetpack Notifications bot visit trigger the cron just like a page request? It’s not just a simple ping?

Thanks,
Kelly

@kellyaz Sorry, I should have been more clear ??

If your scheduling problems are caused by the second cause I listed above, then Jetpack can’t help.

If, however, you scheduling problems happen because of the first cause (not that many people visiting your site, or at least not around the times when you scheduled posts), then Jetpack’s Monitor module can indeed help, as it is indeed a page request, and not just a ping. If you use WordPress’ default cron system, it will consequently trigger a cron check.

I hope this clarifies things a bit!

Yes it does – thanks!

The only site I am having this issue with just had a soft launch and there are only a few users; there are visits throughout the day but perhaps not very many, so it sounds like Monitor may help!

Still, I’m having a little trouble understanding one aspect of this. It doesn’t seem WP fails to post a scheduled post if someone visits the site a minute or two after the scheduled posting time; otherwise if it required the visits to almost perfectly coincide with post schedules in order for them to run, this would be a widespread problem.

There must be a set interval between scheduled time of post and latest run of the WP-Cron that determines what is and isn’t missed. It would seem like any future run of the cron would attempt to post all past missed scheduled posts? Why can’t it do that?

thx!

There must be a set interval between scheduled time of post and latest run of the WP-Cron that determines what is and isn’t missed. It would seem like any future run of the cron would attempt to post all past missed scheduled posts? Why can’t it do that?

I’m afraid I don’t know enough of the WordPress scheduling system to answer that question. There must be an interval, but I don’t know what it is.

Another alternative to fix all this would be to use a plugin like this one to force trigger all scheduled posts to be published.

@bfdbookblog I noticed you are having scheduled blog issues. I too use GoDaddy and have spent time on the phone with them for probably now over 10 hours of time. I get the run around but what @jeherve has said above with #2, that is not happening, according to GoDaddy. I’m told that they do not touch that file and that it comes as is when we get Managed WordPress. The only modifications made to that file would be a plugin that touches it, say Jetpack for example. I have not been working with scheduled blogs now since September 14th around the time Jetpack went to version 4.3. I have gotten the missed schedule status as well and have “Monitor” active with Jetpack and yet it still does nothing to get my publicize to work correctly. I’m trying to see if maybe we have something similar in configurations. What other plugins do you have active and what theme are you using… just curious. And have you seen the scheduled blog work in the past few days?

I have not had schedules work for 2 weeks. Nothing suggested has made a difference. I too have spent time chatting with GoDaddy with the same result. The additional plugins I’m using are as follows:

Akismet Version 3.2 | By Automattic
Module Control for Jetpack Version 1.4.2
WordPress Editorial Calendar Version 3.6.2
WordPress Importer Version 0.6.3

I am using the Creative Blog Version: 1.0.1 theme.

@bfdbookblog Could you let me know what version of Jetpack you currently use on your site?

Version 4.3.2

Excellent. That’s the latest version, that included a lot of fixes for Publicize.

Can you please use Jetpack’s Debugger module to send us some more information about your site?

1) Go to the Jetpack page in your dashboard.
2) Click on the Debug link appearing at the bottom of the page.
3) Click the link that says “click here to contact Jetpack support.”
4) Fill in the description box and your name and email address. Do not hesitate to mention this thread in the description, so we’ll know more about what you’ve already tried.
5) Click the “Contact Support” button to send us the debug results privately. It’s best not to post this information on public forums, as it contains private details about your site.

Thanks!

Just to give a little feedback; enabled Jetpack’s Monitoring feature did not solve the problem; some but not all scheduled posts still fail.

I had my web host set up a real crontab job to run the wp-cron every 10 minutes; that also did not solve the problem. The method used was as follows:

If anyone comes up with something else to try would love to know!
Thanks!