How to fix Outreach sequence stuck in pending status for hours

When an Outreach sequence is stuck in pending status for hours, the cause is almost always a mailbox sync failure, a delivery schedule that hasn't hit its send window, or throttling limits. Reconnect the affected mailbox, check the sequence schedule and timezone, then verify daily send caps. These three checks resolve most pending-state issues within minutes.

Why Outreach Sequences Get Stuck in Pending

A "pending" task in Outreach means the platform queued the step but hasn't dispatched it. The email exists, the prospect is enrolled, but something between the queue and the mailbox is blocking the actual send. Most teams assume it's a bug. It usually isn't — it's a configuration or sync problem.

Outreach relies on a live OAuth connection to your mailbox (Gmail, Microsoft 365, or Exchange). If that token expires, the platform can't push the message, so it parks the task in pending. The same thing happens when a step is scheduled outside the sequence's active send window or when you've hit a throttle limit.

Mailbox Disconnection or Token Expiry

This is the number one cause. OAuth tokens for Microsoft 365 and Google Workspace expire or get revoked when an admin changes security policies, resets a password, or enables new conditional access rules. Outreach surfaces this under Settings → Email → Mailboxes, but the warning is easy to miss.

If the mailbox shows a red or amber status, disconnect and reconnect it. You'll re-trigger the OAuth flow and refresh the token. After reconnecting, pending tasks typically flush within 5–15 minutes during an active send window.

Delivery Schedule and Timezone Mismatch

Every sequence has a delivery schedule that defines when emails can go out. If your schedule is set to 8 a.m.–5 p.m. Eastern and a task lands at 6 p.m., it stays pending until the next open window. This is working as designed, not a failure.

The trap is timezone. Outreach can use the sequence timezone, the rep's timezone, or the prospect's timezone depending on your settings. A mismatch makes tasks look frozen when they're just waiting for the right clock. Check Sequence Settings → Schedule and confirm the timezone matches what you expect.

Send Limits and Throttling

Outreach enforces per-mailbox daily send caps to protect deliverability. If a mailbox hits its limit — say 500 emails a day — remaining tasks queue as pending until the counter resets at midnight in the mailbox timezone. Microsoft 365 also imposes its own sending limits (commonly 10,000 recipients per day), and Outreach respects those server-side caps too.

Step-by-Step Fix

Work through these in order. Stop as soon as the pending tasks start clearing.

1. Check mailbox health. Go to Settings → Email → Mailboxes. Reconnect any mailbox showing a warning. Re-authenticate through the full OAuth prompt, not a partial refresh.
2. Verify the delivery schedule. Open the sequence, confirm the send window is currently open, and check the timezone. Temporarily widen the window to test if tasks fire.
3. Review send limits. In mailbox settings, look at the daily send cap and current count. If you're at the cap, tasks release after the reset.
4. Confirm sequence and ruleset state. Make sure the sequence is set to active and isn't paused by a team ruleset or admin policy.
5. Force a sync. Trigger a manual mailbox sync if available, or wait one full sync cycle (usually under 15 minutes).

If tasks are still pending after all five steps, the issue is likely server-side and warrants a ticket to Outreach support with the affected mailbox ID and a sample task ID.

Common Root Causes at a Glance

Preventing Pending States Going Forward