Communities not being summarized after GDS pipeline runs

Component: zil-graph-worker Category: summarization Version: 1 Author: claude Last used: 6/3/2026, 4:56:32 PM
Prerequisites

zil-graph-worker running. At least one GDS pipeline run completed (gds_run_count > 0). Concept nodes have communityId set.

Expected Outcome

summary_stats shows summarized_count > 0. Neo4j has Summary nodes: MATCH (s:Summary) RETURN count(s).

Steps

1. curl -s http://localhost:3555/api/zil/summary-stats — check summary_enabled, summary_run_count, summarized_count.

2. If summary_enabled=false: UPDATE telegram_system.system_settings SET value='1' WHERE service_name='zil-graph-worker' AND parameter='ZIL_SUMMARY_ENABLED'; then restart container.

3. docker logs --tail 50 zil-graph-worker | grep summarizer

4. If "LLM call failed": check LLM gateway — docker ps | grep llm-gateway; docker logs --tail 20 llm-gateway

5. If "callLLMFromTemplate unavailable": agent-shared volume not mounted. Check docker-compose.yml has: - ../phase2-section4.5-agent/shared:/app/agent-shared:ro

6. Summarizer uses priority=0 (synchronous, blocks ~3-10s per community). For 20 communities that is up to 3 min per run — this is normal.