Scheduled sends that don't silently stall
Scheduled sends now retry through timing collisions instead of dropping, contacts that go cold again can finally be paused, and you're alerted when a live thread hits the AI reply cap.
A send that quietly disappears is one of the hardest problems to notice — there is no bounce, no error, just a contact who never got the email. We tracked down three of these silent gaps: sends dropped on a scheduling collision, contacts that should have been cold-paused but never were, and hot threads that hit the AI reply cap with no one watching.
What was happening
When the system reserves a precise time slot for a send, two sends can occasionally collide on the same reservation. Both rescheduling an email and the automatic recovery of emails that had failed for a transient reason would hit that collision and simply fail or skip the send rather than working around it — so the email never went out. The cold-pause logic had a subtler bug: it watched a contact's no-engagement streak to decide when to pause them, but once a contact had ever engaged, that streak froze. A prospect who replied early, went warm, and then went completely silent could never be cold-paused, because the system still counted them as someone who had engaged. And when an inbound thread reached the cap on AI auto-replies while the prospect was still actively replying, the conversation just went quiet on your side, with no signal that a live, interested prospect now needed a human.
What we fixed
Send-slot collisions are now handled gracefully: both rescheduling and transient-failure recovery shift the time slightly and retry instead of giving up, so the send goes through. The cold-pause logic was corrected so the no-engagement streak keeps counting after a contact goes cold again — a contact who warmed up and then stopped responding can now actually be paused, the way you would expect. And you now get an alert the moment an inbound thread hits the AI auto-reply cap while the prospect is still replying, so a hot conversation is flagged for you instead of being left unanswered.
Why it matters
These fixes close gaps where activity was being lost without any warning — the worst kind of failure, because there is nothing to notice until you go looking. Scheduled sends that used to vanish on a timing collision now complete, so your sequence reaches every contact it was supposed to. Cold contacts get paused instead of consuming sends and skewing your numbers indefinitely, which keeps your engagement metrics honest and your volume aimed at people who might actually respond. And the most valuable conversations — a prospect who keeps replying — get escalated to you at exactly the point where a human should take over, so your hottest threads do not go cold from neglect at the moment they are most worth your time.