Why hasn't my campaign email gone out yet?

Start with the delays

A campaign email can carry three separate conditions, and it waits for all of them to be true at once.

• A delay in days, hours or minutes since the email before it.
• A time of day it is allowed to go out.
• Days of the week it is allowed to go out.

systeme.io's own worked example: an email set to send two days after email one, at 10:00, Monday to Friday only. Email one lands on a Thursday at 15:00. The two-day delay points at Saturday at 15:00, which is neither a weekday nor 10:00, so the email waits until Monday at 10:00.

Nothing is broken there. Stack three conditions and a wait of several days is the correct result. systeme.io recommends against setting several delays on the same email, to avoid confusion.

Check the email is activated

A newly added campaign email is inactive until it is activated and given a send-after instruction. While it is inactive it shows a grey dot and sits at the top of the list, outside the running order.

An email at the top of a campaign is not necessarily the next one to send. It may be the one that never will.

Check the contact is in the campaign

Contacts do not enter a campaign by existing. Something has to put them there: an automation rule with a Subscribe to campaign action, or a manual subscribe from the contact list under More actions.

A manual subscribe also asks which step the contact starts at. So a contact can be enrolled and already past the email you are waiting on.

Check the contact can receive it

A contact whose status is Unsubscribed or Bounced stays enrolled and keeps moving through the steps on the delays that were set. They receive nothing while that status stands.

The sequence never pauses for them. If the status goes back to subscribed, they pick up at whatever step they have reached by then, not the one they stopped at.

An inserted email does not go backwards

Add an email to the start or middle of a running campaign and only contacts who have not yet reached that point will receive it. Everyone already past it never gets it.

Add one to the end and every contact still subscribed is enrolled for it, because reaching the final email does not remove anybody from a campaign.

The delay on a newly inserted email counts from the date the contact received the previous email, not from the date the email was created. A 24-hour delay added weeks after the fact is already satisfied, so it sends at once.

Changing a delay does not move the people already inside

New conditions apply to contacts who subscribe after the change is saved. Contacts already in the sequence keep the conditions that were in place when they joined.

So an email rescheduled yesterday still goes out on the old schedule for everybody enrolled before the edit.

When the account is the thing holding it

If a send is sitting as pending, the hold may have nothing to do with the campaign. systeme.io runs checks on outgoing mail, and sending it again does not clear them.

• A new account. The first 100 emails go out, then sending is paused while the statistics are read. That check takes anywhere from a few minutes to six hours, and it repeats after every batch of 100 emails until 500 have been sent.
• A fresh import. Sending can be paused after a contact list is imported, while the origin of the list, the state of the addresses and the sending domain are checked.
• The wording. An email containing expressions the system reads as spam is held for a person to review, then released or blocked with a reason given.
• A link. systeme.io reserves the right to block an email carrying a link it considers dangerous.
• Volume. A large send can trigger an automatic check, which lasts a few minutes and clears itself.

The one to be careful with

Deactivating every email in a campaign while contacts are still enrolled, then switching them back on, resends all of them to everybody currently enrolled, including people who already read them. systeme.io's advice is to build a new campaign instead of reactivating an old one.