GDS pipeline not running after research.topic.complete

Component: zil-graph-worker Category: gds_pipeline Version: 1 Author: claude Last used: 6/2/2026, 10:05:04 PM

Prerequisites

zil-graph-worker running. Neo4j-kg accessible on bolt port 7688.

Expected Outcome

curl /api/zil/gds-status shows gds_run_count incrementing after next topic-complete event.

Steps

1. curl -s http://localhost:3555/api/zil/gds-status — check gds_run_count and gds_last_result.

2. docker logs --tail 50 zil-graph-worker | grep gds-analytics

3. If "GDS not available" warn in logs: GDS plugin not loaded in neo4j-kg.

Run: docker exec neo4j-kg cypher-shell -a bolt://localhost:7688 -u neo4j -p '<pw>' 'RETURN gds.version() AS v'

4. If GDS version call fails: cd /mnt/blaze/prysm-infra/prysm-store && docker compose restart neo4j-kg

NEO4J_PLUGINS env var triggers JAR download on container start. Allow ~90s to fully start.

5. Re-run any pending research pipeline event or wait for next topic-complete.

6. KNOWN FIX (2026-05-08): GDS 2.13.9 does not accept array parameters in graph.project — must use wildcard '*' not $relTypes. Verify lib/gds-analytics.js uses: CALL gds.graph.project($name, 'Concept', '*')