Who This Is For / When to Use
Accounts sending newsletters via RSS Email campaigns
Teams setting up recurring blog or newsletter email-outs
Administrators troubleshooting RSS emails that appear to "reschedule themselves"
How RSS Email Campaigns Work
RSS Email campaigns are event-driven, not time-driven.
This means:
The scheduled time defines when the system checks the RSS feed
An email is sent only if new RSS content exists
If no new content is found, no email is sent.
The RSS Content Time Window (Critical Rule)
An RSS Email is triggered only if at least one RSS item meets all of the following conditions:
The RSS item is published after the RSS email campaign is created
The RSS item is published before the scheduled execution time
This time window is strict. If an RSS item was published before the campaign existed, it is ignored.
What Happens When No New RSS Content Exists
If the system finds no qualifying RSS items during a scheduled run:
No email is sent
No error is shown
The campaign is marked as skipped
The execution date automatically moves to the next interval
This is expected behavior. The campaign list always shows the next scheduled execution, not skipped runs.
Why This Often Looks Like a Bug
This behavior is commonly misinterpreted because:
The campaign appears scheduled correctly
Test emails send successfully
The scheduled time passes silently
The send date updates to a future date
In reality, the campaign ran—but found no new RSS content to send.
Correct Setup Order for RSS Email Campaigns
To ensure RSS emails send reliably:
Create the RSS Email campaign first
Add RSS blocks
Add the RSS feed URL
Set frequency (daily, weekly, monthly)
Set the desired send time
Leave the campaign enabled
Publish blog posts or RSS content after the campaign exists
At the next scheduled execution, the new content will be detected and emailed.
Important Warnings and Common Mistakes
Do Not Expect Retroactive Sends
RSS Email campaigns do not send previously published content.
If content already exists before the campaign is created, it will not trigger a send.
Avoid Editing or Recreating Active RSS Campaigns
Each time you:
Edit the RSS email
Duplicate or clone the campaign
The campaign’s effective "created" timestamp is reset.
This can invalidate existing RSS items and cause skipped sends.
Do Not Click the Refresh Button Unless You Intend to Skip
The Refresh button on RSS emails:
Does not resend emails
Forces the campaign to move to the next execution date
Only use Refresh if you intentionally want to skip the current cycle.
Time Zone Considerations
RSS Email scheduling uses the account’s configured time zone.
For multi-region setups:
Confirm each account’s time zone matches the intended audience
Time zone mismatches may cause confusion when reviewing send times
How to Test RSS Emails Correctly
To validate an RSS Email campaign:
Create and schedule the RSS Email campaign
Publish a new blog post to the connected RSS feed
Confirm the post publishes after campaign creation
Wait for the next scheduled execution
If the RSS item meets the time window, the email will send.
FAQ
Why did my RSS email not send at the scheduled time?
The campaign did not find any new RSS items published after the campaign was created and before the scheduled send time.
Why does the execution date keep moving forward?
When no qualifying RSS content is found, the campaign automatically advances to the next scheduled run.
Do test emails validate RSS scheduling?
No. Test emails send immediately and do not confirm RSS scheduling behavior.
Can RSS emails send previously published posts?
No. RSS emails only send content published after the campaign is created.
Should I create a new RSS campaign for each post?
No. Create one recurring RSS campaign and leave it enabled. Publish new posts as needed.
What happens if I edit an existing RSS campaign?
Editing resets the campaign’s effective creation time, which may cause upcoming sends to skip.
Key Takeaway: RSS Email campaigns must exist before new RSS feed content is published. They are designed to automatically email future posts—not past ones.