renewal reminder not sent: automation failed before contract end

TL;DR

Renewal reminders fail by calendar logic: the automation computes from the wrong date field, excludes the segment, or its send window already passed when the contract was loaded late. Rebuild the reminder timeline for one missed renewal from the automation's own rules and find which condition silently dropped it.

renewal reminder not sent: automation failed before contract end

Use this when

• Accounts reached renewal with no reminder email or task
• The automation exists and works for other segments
• Contracts may be loaded into the CRM after signature with delays

Not for this skill when

• The reminder sent to an outdated contact and bounced
• CSMs send manual reminders and the automation was retired intentionally

Steps

1. Take one missed renewal and compute when the automation should have fired from its configured rules. Verify: the expected fire date is known
2. Check the account against each audience and entry condition as of that date. Verify: the condition that excluded the account is identified
3. Verify the date field the automation reads against the contract's real end date. Verify: any wrong-field or late-load issue is confirmed
4. Fix the condition or field, then run a catch-up pass for all renewals inside the reminder window. Verify: every at-risk renewal gets its reminder or a CSM task now
5. Add a weekly no-reminder-yet report for renewals due in 60 days. Verify: a miss is visible while there is still time to act

Variant phrasings

renewal reminder never sent

A related phrasing for the same underlying problem.

automation missed contract end

A related phrasing for the same underlying problem.

renewal approaching no outreach

A related phrasing for the same underlying problem.

Compatibility: Compatibility: marketing and CRM automation (HubSpot, Marketo, Salesforce flows) driven by contract dates, current versions.

Why it happens

Automations evaluate conditions at a moment in time; an account that becomes eligible late, or whose date field is wrong, is not failed loudly, it is simply never selected. Reconstructing one account's expected timeline exposes which silent exclusion applies, and the catch-up pass matters as much as the fix.

Edge cases / pitfalls

• Late-loaded contracts need an eligibility sweep that catches accounts already inside the window, not only those approaching it.
• Reminder audiences built on billing contacts miss accounts whose billing contact left. Include the CSM task as a parallel path.
• A reminder is not a renewal strategy. The report should feed human outreach for high-value accounts, not just more email.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst-b44DKzXf3yppCi9OhLbQ