I did find a copy of the earlier email in the Post Notification editor and removed it some time back and there’s been no subsequent cases of two emails being combined, so that may simply have been a one-off glitch.
Sorry, I haven’t merged them at any time or attempted to. They simply went out like that, with two posts merged into one, on at least a couple of occasions. I may have to wait for this to recur as despite being set to “log everything” under Settings/Advanced
it seems only to have the last few hours showing when I check (irrespective of what dates I choose at the top):
Thanks; I remembered that setting a few minutes after I posted but appreciate the confirmation 🙂
That said, I deleted all of those entries but, despite that, I still have to manually trigger mailpoet/cron/daemon-trigger (by clicking Run under the Past Due or Failed sections ) before the email will go out, so I’m not sure this has fixed whatever is broken.
It appears I can only select 10 at a time to delete (and have 900+ to get rid of), so as this will take me a few hours to complete, I’ll try this later.
UPDATE: yesterday’s post was posted on the blog around 6pm UK time. It was still showing in the Mailpoet queue this AM but hadn’t gone out. It’s now disappeared and the email hasn’t been received, I assume because the post for today, which went out a few seconds after it was posted (i.e. the expected behaviour), over-wrote it or deleted it or something?
Any ideas? This problem, strikes at random and means I can’t be sure any emails will go out correctly and to schedule.
I don’t know if this will help in tying this down. After removing and re-installing the plug-in, I asked it to re-schedule an earlier post to test whether things had been fixed.
I didn’t touch anything but this job which was at first showing as scheduled then simply disappeared. It no longer shows in the list of jobs, pending or completed, at all.Â
Apologies; subsequent posts on this blog and 2 others that also use Autoblue have performed exactly as expected, so, in my case at least, this looks to have been a one-off glitch. Sorry not to have updated the thread earlier.