Background Email Queue: what it does

By default, WordPress sends email synchronously: your visitor waits while wp_mail() negotiates with an SMTP server. NimblyMail moves every send into an Action Scheduler-backed queue with priorities, claim-based concurrency, attachment staging, and exponential-backoff retries — so checkouts stay fast and provider hiccups never drop an email.

Background Email QueueActive · configured via setup wizard

Enabled

Deliverability auditVerifies configuration weekly

Passing

Why it matters

What you get with Background Email Queue

Zero blocking sends

wp_mail() returns instantly; the queue dispatches in the background. Page loads and checkouts stay snappy.

Three priorities

HIGH for password resets and receipts, NORMAL for notifications, BULK for newsletters and digests.

Exponential-backoff retries

Transient provider errors retry on a widening schedule instead of dying silently.

Attachment staging

Large attachments are staged off the queue payload, so a 10 MB invoice PDF never stalls dispatch.

How it works

Three steps, zero babysitting

Email enters the queue

Any plugin calls wp_mail(). NimblyMail captures the message, assigns a priority, and returns immediately.

Workers claim and send

Action Scheduler workers claim jobs with concurrency limits — no duplicate sends, even on busy multisite installs.

Failures retry or fail over

Errors retry with exponential backoff. On Pro, a backup mailer takes over automatically after the retry budget is spent.

FAQ

Background Email Queue questions, answered

Does the queue slow down my site?

No — the opposite. Sending email synchronously can add 1–3 seconds to form submissions and checkout. With the queue, wp_mail() returns in milliseconds and Action Scheduler dispatches in the background via WordPress cron.

What happens to queued email if my provider is down?

Can I prioritize order receipts over newsletters?