E-mails for re-scheduled posts still deploy at original time

Could you please walk me through the steps you follow to schedule a post? I’m not sure I understand how you “re-schedule” a post.

Hi Jeremy! Thanks for getting back to me! To schedule a post I click “Edit” next to the “Publish Immediately” text in the Publish box on the individual post page. Then I select/enter the date and time I want, press “OK”, and then press “Schedule”.

If I decide I want the entry to go up at a different time, I will simply change the date and time in that same place by hitting “Edit” next to the “Scheduled for:” text, choosing a new time/date, and hitting the “Update” button. Lately, though, the e-mails for these re-scheduled posts still go out, even though the entry does not publish. Then, when that re-scheduled post does publish, no e-mail goes out.

Thanks!

Alright, I understand. So the problem only happens when you schedule a post twice. I will try to reproduce the issue on a test blog of mine, and let you know as soon as I have some news.

I’m afraid I wasn’t able to reproduce the issue. When going back, changing the scheduling date, the posts are not publicized, and are only publicized when the post is finally published.

Do you use any other plugins that may affect the status of your posts? if so, could you try to deactivate them, and let me know if it helps?

I don’t think I do have any plug-ins that effect the status of my posts (they are mostly things like automated back-ups, social network icons, a related posts engine, a comments captcha, and Google Analytics). I don’t actually have JetPack’s “publicize” hooked up, it’s just the automatic e-mails that go out. If I check my day-to-day page view chart and hover a re-scheduled day, it will list 2 posts as being published, even though one of them was re-scheduled and did not actually go live. It occurs to me that this could be an error that has nothing to do with JetPack, but I am fairly certain that all my subscribers are run through JetPack (the subscription widget is JetPack run, and the JetPack page is the only place I see how many subscribers I have).

Could you send me a few examples of the posts that were sent to your subscribers before being published?
You can use this contact form to contact us directly:
https://jetpack.me/contact-support/

Thanks!

Sure thing! Can you let me know exactly what you need? Just the text, screen caps of the post drafts, etc.?

Links to these posts would do fine, along with the scheduled date and the date and time when the posts were actually sent to your subscribers.

Thank you.

Most of the posts have no actually published yet, but they’ll be going up this soon.

https://wp.me/p1Td2W-1hZ
E-mail sent May 3, due to publish May 25

https://wp.me/p1Td2W-1ju
E-mail sent May 4, due to publish May 19

This post (https://wp.me/p1Td2W-1hU) I simply un-scheduled and moved back to drafts so I could publish something I was currently working on, and the e-mail still sent at the original publishing date (April 28, 12:15PM MDt), so I pushed it live right away since it had already been e-mailed out.

The last one (https://wp.me/p1Td2W-1hU) is the first time this error happened.

Thanks!

Could you post a list of your active plugins here? I’ll try to add them all to my test site to try to reproduce the issue once again.

OK! They are:

• Askimet
• All in one Favicon
• Alpine PhotoTile for Instagram (not installed when the problem began)
• Automatic Post Tagger
• Dynamic Content Gallery (not installed when the problem began)
• Google Analytics
• Google Web Fonts Manager
• Jetpack by WordPress.com
• Multicons
• nrelate Related Content
• Really simple Facebook Twitter share buttons
• Simple Author Highlighter
• Simple Twitter Widget
• TheThe CAPTCHA
• UpdraftPlus — Backup/Restore
• WordPress Hit Counter
• WP Calais Archive Tagger

Looking at that list there’s a few I could get rid of, but in the interest of getting to the bottom of this I won’t change anything at the moment.

Also, when this post (https://wp.me/p1Td2W-1ju) went out yesterday, the e-mail didn’t go out until I moved it back to drafts and then re-published it, which probably has something to do with the e-mail going out on May 4.

Thanks for that list!

I have asked our Subscription expert to have a look at the problem, and I will get back to you as soon as I have some news.

In the meantime, do not hesitate to let me know if things get better in the coming few days!