--- title: "KnovvuCANoAnalyzedConversations" slug: "runbooks-knovvu-analytics-ca-no-analyzed-conversations" updated: 2025-05-19T13:13:32Z published: 2025-05-19T13:13:32Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.knovvu.com/llms.txt > Use this file to discover all available pages before exploring further. # KnovvuCANoAnalyzedConversations ## Meaning This alert indicates that no new call or chat conversations of a particular type have been analyzed by Knovvu Analytics in the last 24 hours. It suggests that the analysis pipeline, managed by the `ca-analysis` service, may be stalled. The alert is triggered at the warning level if this condition persists for 30 minutes.
Full context Knovvu Analytics continuously processes conversations to generate insights for contact center operations. Conversations are ingested into the platform via the `ca-external-api` service and analyzed by the `ca-analysis` service. If no analyses are completed for a specific type (e.g., inbound calls, chat interactions) over a full day, this may indicate a data ingestion failure, processing engine issue, or system misconfiguration.
## Impact If no conversations are being analyzed: - Business reports and dashboards may become outdated. - Real-time quality monitoring and compliance checks could fail. - Supervisors and analysts may lack visibility into agent or customer behavior. - Root causes of operational issues may go undetected. ## Diagnosis - Review analytics dashboards for conversation activity trends over the past 24–48 hours. - Check the health and logs of the `ca-external-api` service to confirm whether conversations are being ingested. - Inspect the `ca-analysis` service to ensure it is processing incoming data and not stalled. - Look for any recent deployment, configuration, or infrastructure changes. - Determine if the issue affects a specific conversation type or the entire pipeline. ## Mitigation - Restart or redeploy the `ca-analysis` service if it is unresponsive or idle. - Verify that the `ca-external-api` service is functioning and receiving conversation data from external sources. - Check for backlog or errors in the processing queues. - If expected to be a low-volume period (e.g., holidays or system downtime), document the reason and silence the alert as appropriate. - Escalate to the development team if the issue persists and the root cause is unclear.