At a glance: Sometimes an email sends right away; sometimes it’s queued and retried if your mail provider hiccups. If we couldn’t auto-write a perfect draft, we still open a task so you can type the message yourself. We also try not to nag people who already replied or who sent an out-of-office reply.
Email didn’t send (yet)
We may send in the background so you’re not stuck on a loading screen. Give it a short time and refresh.
If your email provider errors, we’ll retry a few times with increasing wait times, up to a cap set for the product.
If retries are exhausted, you’ll need to fix the underlying issue (often reconnecting email) and try again from the task or thread.
We try to avoid double-sending if your network blips and the same action runs twice—one send per approval is the goal.
Blank or generic drafts
If automatic drafting isn’t available or we’re missing context, we still create a task with a simple placeholder so you’re never blocked—replace it with a real subject and message before you send.
They replied—why didn’t the next automated email go out?
When we detect a real human reply, we may stop the next automatic nudge so you don’t keep emailing after they’ve answered.
An out-of-office or auto-reply may pause the sequence. If the message includes a return date, we try to respect it; otherwise we may wait a few days before continuing.
Quick fixes when something looks stuck
What you notice | What might be going on | What to try |
Send error or “provider” error | Mailbox disconnected, quota, or provider issue. | Reconnect email in Settings; retry send; wait a bit if we’re retrying in the background. |
“Missing” recipient or empty draft on auto-send | We don’t have an address or a complete message. | Open the task, fill in recipient/subject/body, send again. |
Reply failed in an existing thread | The thread or recipient couldn’t be matched for a true reply. | Check the thread in Outreach; if your plan allows a fresh email instead of a reply, use that path. |
Run shows “waiting” forever | The timer isn’t up yet, or processing is slightly delayed. | Check Runs for a “resumes…” hint; wait until after that time. |
Run waits for you | A task needs your approval or edits. | Open Tasks and complete the pending item. |
Contacting support
Include: roughly when it happened, the job (title and company), the error text if you saw one, and whether you were on Tasks, Runs, or Threads. Don’t share passwords or private tokens.
Related articles
See where a follow-up sequence stands, Review emails before they go out, Read and reply to your emails.