// Reference
Limitations & FAQ
What Renewal Radar treats as production renewal evidence today, which dates stay excluded, and how uncertainty affects automation.
Current product boundaries
- Company, Deal, Subscription, Line item, Quote and eligible custom-object sources can be production-authoritative when they pass the deterministic semantic and record gates.
- Generic Quote expiration, billing/payment cadence, forecast/operational and created/modified dates remain excluded from authoritative renewal timing.
- No AI, predictive churn model, sentiment analysis, or health score.
- No reading of email bodies, note bodies, call recordings, meeting notes, or ticket content.
- Renewal alert window is 30, 60, or 90 days.
- No real-time CRM object webhooks. Scanning is periodic and can also be triggered manually.
- The record card lives on Company records. Portfolio and configuration views live in Renewal Radar settings.
Automatic source detection
You do not need to pick one contract-end field or confirm one portal-wide source. Renewal Radar discovers supported renewal semantics and resolves timing separately for each Company.
A Company can resolve from eligible Company, Deal, Subscription, Line item, Quote or relevant custom-object evidence, a renewal-specific proxy, an estimate, or no reliable current timing. Estimates remain Low-confidence and task-ineligible.
Task-safety limitations
A High or Critical Renewal Risk does not automatically create a task. The canonical timing must also be task-eligible, the Company must allow tasking, and the task lifecycle/control policy must allow creation.
Medium/Low timing confidence, proxies, estimates, material conflicts, no timing, and incomplete authoritative evidence fail closed for new task creation. Engagement Risk by itself is visibility, not a standalone task trigger.
If required data is temporarily incomplete or unavailable, Renewal Radar does not treat that as evidence that an existing active risk disappeared.
Scan performance
Renewal Radar performs portal-wide candidate discovery before the expensive account-level signal checks. If complete candidate recall cannot be proven, it falls back to the broader Company inventory rather than silently filtering possible renewals.
The latest production read-only validation considered 24,159 Companies, processed 375 canonical candidates, and completed in 12m33s with zero failed Companies. CRM Search completed with zero 429s and zero retries under the production limiter.
Common questions
Does Renewal Radar use AI to decide which date is correct?
No. Source classification and timing resolution use deterministic, versioned rules. Runtime resolution does not use an LLM, embeddings or fuzzy matching.
Is a mapped Company contract end date required?
No. Renewal source discovery is automatic and can resolve from eligible Company, Deal, Subscription, Line item, Quote or relevant custom-object evidence.
Can an estimate create a task?
No. Estimates are Low-confidence monitoring timing and are task-ineligible.
Does Engagement Risk create a task?
No, not by itself. Engagement Risk is supporting visibility and can explain or mitigate Renewal Risk.
What happens when HubSpot data is temporarily unavailable?
Incomplete evidence blocks unsafe new automation and preserves existing active state until a complete authoritative decision is available.
Where can I see the performance evidence?
The published speed and accuracy benchmark documents the 24k-company before-and-after, and the current docs include the latest 12m33s production validation with zero CRM Search 429s.