Scheduled Email Campaigns in Mailbase

Overview

Mailbase scheduled campaigns are real workflow records, not a UI-only delay. The campaign stores the scheduled timestamp and timezone, validates that the send is at least 15 minutes in the future, and can be edited or cancelled from the campaign detail page before it leaves draft control.

How Scheduling Works

The campaign wizard can launch now or save a scheduled send. Scheduled campaigns keep the timezone alongside the timestamp so the detail page can show both the planned time and a countdown.

When the internal send-job worker runs, it enqueues due scheduled campaigns into the same durable sending path used by immediate launches. That keeps scheduled sends observable and retryable instead of depending on an open browser session.

• 15-minute minimum lead time
• Stored scheduled timestamp and timezone
• Campaign detail countdown
• Reschedule and cancel controls
• Worker-driven execution

Operator Controls

Before the scheduled time, the campaign detail page lets a teammate move the send time or cancel the schedule back to draft. Server-side validation repeats the lead-time check so API callers cannot bypass the UI rule.

Lifecycle analytics and server logs capture scheduled, cancelled, executed, and failed states so teams can debug missed windows without guessing.

Common Mistakes

• Choosing a tool before deciding who owns deliverability.
• Treating DNS authentication as a one-time checkbox instead of an operating baseline.
• Mixing product-critical transactional email with experimental marketing sends, with no clear boundary.
• Trusting headline metrics (like open rate) that privacy proxies now inflate.

Sources & Further Reading

Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.

Related guides

More on scheduled email campaigns and the surrounding product workflow: