Post-4.1 rollout repairs

After the 4.1 release, a handful of inconsistencies showed up across read state, warm up separation, campaign AI instructions, and draft handling. This release closes those gaps, so behavior across your inbox and campaigns is consistent again.

What changed

A release of this size touches many parts of the system at once, and a few things did not settle correctly right after 4.1 went out. Read state on inbox threads was not always behaving reliably, meaning a thread could show as read or unread in a way that did not match what actually happened, leaving you unsure whether you had already seen a message or not. Warm up separation, the effort to keep warm up traffic distinct from real inbox activity, was not fully consistent yet in every case, so some warm up messages could still surface where they should not have.

Campaign AI instructions were not always being applied the same way across every part of a campaign, which could mean a setting you configured in one place was not fully respected elsewhere, producing drafts that did not match what you had actually asked for. And in some cases, a stale draft, meaning one based on outdated instructions or research, could slip through into a send instead of being caught and refreshed first, which meant a prospect could receive an email that did not reflect your most recent setup.

These four issues were not related to each other by cause, but they shared a common pattern: each one was a place where the 4.1 release had changed how a piece of state, whether that is a thread's read status, a warm up message's classification, a campaign's instructions, or a draft's freshness, was tracked and applied. Rolling out a release of that scope means updating how the system tracks many small pieces of state at once, and these four were the ones that needed a follow-up pass to fully settle.

Read state on inbox threads is now applied consistently, so what you see matches what actually happened. Warm up separation now behaves correctly everywhere it should, keeping that traffic distinct from your real inbox as intended in every case, not just the common ones. Campaign AI instructions are now applied consistently across every part of a campaign that uses them, so a setting you configure once is respected everywhere it should be. And stale drafts are now caught properly, so a draft built on outdated instructions or research cannot slip through into a send.

Each of these four fixes was verified against the specific behavior it was meant to restore, not just checked for whether the underlying error went away. Read state was tested against real thread activity, warm up separation was tested against the same range of subject formats covered elsewhere in this release, instruction consistency was tested across every part of a campaign that reads from it, and stale draft handling was tested by deliberately changing instructions mid-campaign and confirming the next draft picked up the change correctly.

How to use it

If you noticed inconsistent read or unread counts on inbox threads shortly after 4.1, that should now be resolved. If a campaign seemed to follow your instructions in some places but not others, it should now behave consistently throughout every stage of drafting. And if you were manually double checking drafts to catch anything that might be based on stale instructions, that should no longer be necessary, since the system now catches those before they can send.

If anything still looks inconsistent in your account after this fix, it is worth a fresh look, since these repairs specifically targeted the gaps that appeared right after the 4.1 rollout, and any remaining issue is likely to be something new rather than a leftover from that transition.

If you paused or slowed down any campaigns while these issues were being worked through, this is a reasonable point to bring them back to full activity, since the specific gaps that would have justified caution have now been closed.

It is also a good moment to spot check a campaign end to end: open a recent thread and confirm its read state looks right, glance at the Email Warm Up tab to confirm warm up traffic is staying separate, and re-read a recent draft against the campaign's current instructions to confirm they line up. None of this should take long, and it gives you direct confirmation rather than taking the fix on faith.

Why it matters

Inconsistency is its own kind of bug, even when no single instance looks dramatic on its own. A read count that is sometimes wrong, instructions that apply in some places but not others, or a stale draft that occasionally slips through all chip away at trust in the system as a whole, even when most of the time things work fine. Closing these specific gaps restores the consistency you should be able to count on once a major release has fully settled. A big release earns trust not just by shipping new capability but by following through on the loose ends it leaves behind, and this is that follow-through. If you noticed any of these four gaps in your own account over the past couple of weeks, they should now be resolved, and the behavior you see going forward should hold steady rather than needing another round of fixes.

The larger point behind a release note like this one is not any single fix, but the discipline of going back and closing every gap a big change opened, rather than moving on once the headline features were live and stable. That follow-up work rarely makes for an exciting announcement, but it is what makes the features underneath it something you can actually rely on day to day, without having to wonder whether a given account or campaign quietly slipped through a rollout gap that nobody circled back to close before the team moved on to whatever came next on the roadmap.

Availability

These repairs are live now for every account and every campaign. There's no toggle to flip and no setting to update on your side.