docproc: a new error shape, 9× in the last hour, never seen in 90 days (NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-)
warning
Error never seen before
delta
open
impact 37
Owner: Sambasiva Bandarupalli (backup: Ahmed Aburaed)
opened 3d ago · last observed 3d ago · observed 4× · #17302 · eed78ebecf5906753f12
What happened template
docproc logged “NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:?” 9 times in the last hour and never before in 90 days on delta (first seen 2026-11-15 06:27 UTC, raised at tilda_neo4j/client.py:224). Example trace: 4cb59cd22862cd23449a04c4de5a8391.
An error shape appearing for the first time in 90 days, five or more times in an hour.
The facts
| service | docproc |
| caller | tilda_neo4j/client.py:224 |
| shape | NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:? |
| count | 9 |
| error_class | — |
| first_seen | 2026-11-15 06:27:51 UTC (3d ago) |
| sample | NEO4J EXECUTE_READ [FAILED] 0.00s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:7687 |
| trace | 4cb59cd22862cd23449a04c4de5a8391 |
| shape_hash | ae785e65dc96ffe1 |
| count_is_floor | no |
| discriminator | ae785e65dc96ffe1 |
| window | 2026-11-15 06:17:13 UTC → 2026-11-15 07:17:13 UTC |
What is failing in docproc — the bad events, decomposed
“Bad events” are HTTP 5xx answers from docproc. In this finding's window (2026-11-15 06:17:13 UTC → 2026-11-15 07:17:13 UTC) there were 0; every line links to the grouped errors behind it.
The error shapes behind them
| 13× | Read query failed — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:7687 since 2026-11-14 06:32:11 UTC |
| 10× | Unable to retrieve routing information since 2026-11-14 06:31:43 UTC |
| 9× | NEO4J EXECUTE_READ [FAILED] 0.00s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:7687 since 2026-11-15 06:27:51 UTC |
| 8× | NEO4J EXECUTE_READ [FAILED] 0.01s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:7687 since 2026-11-14 06:32:37 UTC |
| 2× | Read query failed — {code: Neo.ClientError.Statement.SyntaxError} {message: Invalid input 'UNION': expected an expressio… since 2026-11-07 13:41:22 UTC |
The story — No docproc deploy or hand change is recorded in the hour before this opened. Everything below is docproc only.
- 2026-11-15 06:28:58 UTCthis finding docproc: a new error shape, 9× in the last hour, never seen in 90 days (NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-)
History
- 2026-11-15 06:28:58 UTCopened x-ray · severity=warning title=docproc: a new error shape, 8× in the last hour, never seen in 90 days (NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-) finding={'id': 17302, 'fingerprint': 'eed78ebecf5906753f12', 'kind': 'error.novel', 'severity': 'warning', 'cluster': 'delta', 'subject': 'docproc', 'title': 'docproc: a new error shape, 8× in the last hour, never seen in 90 days (NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-)', 'facts': {'service': 'docproc', 'caller': 'tilda_neo4j/client.py:224', 'shape': 'NEO4J EXECUTE_READ [FAILED] ?00s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:?', 'count': 8, 'error_class': None, 'first_seen': 1794724071, 'sample': 'NEO4J EXECUTE_READ [FAILED] 0.00s — Cannot resolve address neo4j-neo4j-delta.neo4j-system.svc.cluster.local:7687', 'trace': 'b7208e1b3a7d19b56391a80ebf5fb035', 'shape_hash': 'ae785e65dc96ffe1', 'window': [1794720538, 1794724138], 'count_is_floor': False, 'discriminator': 'ae785e65dc96ffe1'}, 'evidence': [{'label': 'Errors, grouped', 'href': '/errors?cluster=delta&from=1794720538&to=1794724138&service=docproc'}, {'label': 'Logs', 'href': '/logs?cluster=delta&from=1794720538&to=1794724138&service=docproc&severity=ERROR'}, {'label': 'Example trace', 'href': '/trace/b7208e1b3a7d19b56391a80ebf5fb035?cluster=delta'}], 'provenance': {'source': 'live', 'collected_at': None, 'age_seconds': None, 'stale': False, 'shown': None, 'total': None, 'truncated': False, 'coverage_from': None, 'retain_days': None, 'note': 'Cloud Logging, last hour, grouped by (service, caller, shape)'}, 'impact': 36.0, 'status': 'open', 'first_seen': 1794724138, 'last_seen': 1794724138, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1, 'narrative': None, 'narrative_kind': None, 'discriminator': 'ae785e65dc96ffe1', 'level': 'medium', 'told_level': None, 'episode_at': 1794724138, 'chat_thread': None, 'kind_label': 'Error never seen before', 'group': 'Errors', 'age_s': 32, 'stale_s': 32}
Check it yourself
Every link carries the finding's own time window, so it shows tomorrow what it shows now.
Actions
Sign in (IAP) to acknowledge, snooze or resolve.
Where the numbers come from
| source | live |
| collected_at | None |
| age_seconds | None |
| stale | False |
| shown | None |
| total | None |
| truncated | False |
| coverage_from | None |
| retain_days | None |
| note | Cloud Logging, last hour, grouped by (service, caller, shape) |
| detector | errors_novel |