FrequentlyAsked Question / Exact Problem
- “Cohort analysis is giving a network error for V2 Retail.”
- “A saved cohort is visible in the Cohort List but cannot be selected inside Journey Builder.”
- “Cohort date filter is not working properly.”
Affected Tenant / Context
V2 Retail (network error on cohort + bucketing), Taruni (cohort not visible in JB), general.
Root Cause
- Cohort queries timing out on large datasets — For high-volume tenants like V2 Retail,cohort queries were taking 30–60 seconds and frequently timing out. Root cause: missing indexes and full table scans in CH.
- Category missing for cohort — For Taruni, a saved cohort was not showing inside the Journey Builder because its category was missing (not assigned when saving). The JB filters cohorts by category, so cohorts without a category are invisible there.
Common Debugging Steps (For CS Team)
- If cohort doesn’t appear in Journey Builder: check if the cohort has a category assigned
(visible in the Cohort List page). If category is blank, this is the issue. - If cohort gives “network error”: note the tenant name, cohort configuration, and exact time. Escalate to dev.
- For large tenants (V2 Retail, Pepe): avoid running multi-segment cohort analysis during peak business hours.
Fix Made & Developer Conclusion
- Cohort not visible in JB: Category field was added manually. Dineshr fixed with Dharshini’s help. Resolution: minutes.
- V2 Retail cohort performance: Post-optimization metrics — Single segment: 30–60s → ~5s. Multi-segment count: Failing → ~5–15s. Multi-segment filters: Failing → ~10–30s.
Exact Dev to Reach Out To
Dineshr — Cohort category fix, quick triage
Dharshini — Cohort query optimization (CH), V2 Retail performance