Scheduler is way off

  • Three times now when scheduling a newsletter to go out, it has not gone out at the right time. I scheduled a newsletter to go out at 9pm that night. This was around 3pm in the afternoon that day. Next thing I know, the newsletter is being sent out at 4pm same day.

    Yesterday I scheduled two newsletters to go out today. One was to go out at 8am and the second at 9am. The first newsletter was still sending at 9:30am and it wasn’t even close to finished. The second newsletter hadn’t even started to send and it was already thirty minutes past when it was supposed to start. I have the rate set at 50 every fifteen minutes and the list is only 125 emails, so it should have sent everything by 8:30am and 9:30am respectively. Once something is scheduled, you also can’t go in and modify it. There’s no option to do this other than duplicating the newsletter and then deleting the original.

    Until this is fixed, I’m afraid to use the schedule feature and will have to send manually, which eliminates the usefulness of the schedule function.

    • This topic was modified 8 years, 5 months ago by pharmedquest.
Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi

    Just in case my own experience could help you…

    I assume you have a cron task to trigger the emails. If you haven’t this could explain why it starts one hour (or whatever random value trigered from activity) later than expected

    However your problem looks like a performance one. In my case I had a similar problem and the root cause was that I had a lot of active debug options left. In debug mode every hourly batch did not even finish at the end of one hour, whilst in non-debug mode it took only 3-4 seconds to send all the batch (80 subscribers per batch). If you have active options in production, deactivate them and see what happens.

    By the way, duplicating the newsletter has a side effect. If you duplicate the newsletter, the copied newsletter will resend all posts even those that were already sent in the past (a bad idea). The reason is that each newsletter has an internal unique Id and keeps track of the posts already sent for that Id. When you duplicate it, a new Id is created and every post looks like a new one for this copied newsletter so it has to send everything again (all your bloc posts!!!). Try it sending yourself a sample from the customization options to check this behaviour.

    Instead of duplicating, it is better to manually force the sending. Though it will resume at the same speed as earlier … so if you have a debugging problem you should deactivate those options before resuming the batch.

    Best regards

    Zulok

    Thread Starter pharmedquest

    (@pharmedquest)

    Thank you so much for these tips. I will work with my webmaster and see if doing these things will help with the timing problem.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Scheduler is way off’ is closed to new replies.