Campaign logs show pending retries
Send errors that are scheduled for retry now appear in campaign logs, so you can see recovery happening instead of wondering.
A campaign log that goes quiet when a send hits trouble is worse than no log at all. It looks like nothing is happening when the system is actually working to recover. That gap between reality and what the logs showed is now closed: send errors scheduled for retry appear in the campaign log the moment they're queued, so you can watch recovery happen in real time instead of wondering whether your campaign is stuck.
Better visibility into sending
When a send hits a temporary error — a soft bounce, a momentary provider hiccup, a send that needs a second attempt — the campaign log now shows the pending retry rather than silently working in the background.
Campaign logs show pending retries
What changed
Campaigns handle transient failures automatically. A soft bounce, a momentary provider hiccup, a send that needs a second attempt — recovery has always happened. What was missing was any sign of it in the logs. Before this update, an email that hit a temporary error and scheduled a retry was invisible until it either succeeded or failed permanently. If you checked the Logs tab in between, the gap looked like nothing was happening. For campaigns sending at any real volume, that silence was easy to misread as a stuck or broken campaign.
Now retry entries appear inline as soon as they're scheduled — for example, Soft bounce retry scheduled — with the same timestamp and contact context as any other log event. You can watch recovery unfold in real time instead of guessing whether the campaign is working.
How to use it
- Open a campaign and switch to the Logs tab.
- Retry entries appear inline alongside sends, opens, and replies — no separate view needed.
- The stat counts in the log header are now clickable: tap any figure to jump straight to the matching entries in the list without manual filtering.
Why it matters for outreach at volume
At low send volumes, an invisible retry is easy to ignore. At the volumes that matter for a real pipeline, invisible retries create anxiety: is the campaign stuck, or recovering? Is this contact going to be skipped entirely, or just delayed? Seeing the retry entry answers those questions immediately and removes the guesswork from reading your campaign health.
The clickable stat counts are a separate but related improvement. Drilling from a summary number directly to the contacts behind it — opens, replies, bounces, retries — cuts the time it takes to investigate anything unusual. What used to require manual filtering now takes one click.
Also in this release
The wait-delay node in the campaign workflow editor now has a proper configuration panel, so setting a delay between sequence steps works as expected rather than requiring workarounds.