execsvc: a new error shape, 5× in the last hour, never seen in 90 days (failed to create document copy — could not add document context: could)
critical
Error never seen before
master
open
impact 58
Owner: Madhava Mukkamala (backup: Shashank Agrawal)
opened 2d ago · last observed 1d ago · observed 3× · #17469 · 3342d84e380a2b2a3153
What happened template
execsvc logged “failed to create document copy — could not add document context: could not write context scope binders: Neo4jError: Neo.TransientError.Transaction.DeadlockDetec” 5 times in the last hour and never before in 90 days on master (first seen 2026-11-16 16:49 UTC, raised at doclib/copyDocument.go:74). Example trace: f91346437409440b0cc533d78b9297f2.
An error shape appearing for the first time in 90 days, five or more times in an hour.
First look — investigated before anyone looked
Cause not clear from logs and recent changes; execsvc document copies failed on Neo4j DeadlockDetected in one burst at 16:49 UTC (5x here at doclib/copyDocument.go:74 via context.go:335 scope binders).
The same burst produced 12x bulk-write deadlocks (createDocument.go:1015, copyDocument.go:74), 14x at tildadb/util.go:993 and 5x at util.go:1004, opening 4 sibling findings.
The deadlock shape at util.go:993 was already seen on 2026-11-15 07:38, so deadlocks predate this burst; the new part is which callers hit them.
Checked: the 5 deploys in the prior 24 h were autosync config-only changes (the latest at 15:39, 69 min before onset), with no image or commit change and nothing tying them to these writes.
Next step: open the example trace to see which concurrent copy transactions took the locks on the scope binders.
Also check whether copyDocument retries Neo.TransientError.
low confidence
claude-opus-5-5 · 2d ago · $0.05 — every link above is evidence it read; nothing else was claimed.
The facts
| service | execsvc |
| caller | doclib/copyDocument.go:74 |
| shape | failed to create document copy — could not add document context: could not write context scope binders: Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId= |
| count | 5 |
| error_class | neo4j |
| first_seen | 2026-11-16 16:49:02 UTC (2d ago) |
| sample | failed to create document copy — could not add document context: could not write context scope binders: Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId= |
| trace | f91346437409440b0cc533d78b9297f2 |
| shape_hash | 46565ad41f6336fc |
| count_is_floor | no |
| discriminator | 46565ad41f6336fc |
| window | 2026-11-16 16:34:53 UTC → 2026-11-16 17:34:53 UTC |
The story — No execsvc deploy or hand change is recorded in the hour before this opened. Everything below is execsvc only.
- 2026-11-16 16:00:00 UTClatency execsvc p95 peaked at 1.51 s
- 2026-11-16 16:55:04 UTCfinding · critical execsvc: a new error shape, 12× in the last hour, never seen in 90 days (failed to create document copy — could not write document node and cor)
- 2026-11-16 16:55:04 UTCfinding · critical execsvc: a new error shape, 12× in the last hour, never seen in 90 days (failed to bulk-write document nodes — Neo4jError: Neo.TransientError.T)
- 2026-11-16 16:55:04 UTCfinding · critical execsvc: a new error shape, 5× in the last hour, never seen in 90 days (failed to add document to scope binders — could not write context scop)
- 2026-11-16 16:55:04 UTCfinding · critical execsvc: a new error shape, 5× in the last hour, never seen in 90 days (failed to run cypher in transaction — Neo4jError: Neo.TransientError.T)
- 2026-11-16 16:55:04 UTCthis finding execsvc: a new error shape, 5× in the last hour, never seen in 90 days (failed to create document copy — could not add document context: could)
History
- 2026-11-16 16:55:04 UTCopened x-ray · severity=critical title=execsvc: a new error shape, 5× in the last hour, never seen in 90 days (failed to create document copy — could not add document context: could) finding={'id': 17469, 'fingerprint': '3342d84e380a2b2a3153', 'kind': 'error.novel', 'severity': 'critical', 'cluster': 'master', 'subject': 'execsvc', 'title': 'execsvc: a new error shape, 5× in the last hour, never seen in 90 days (failed to create document copy — could not add document context: could)', 'facts': {'service': 'execsvc', 'caller': 'doclib/copyDocument.go:74', 'shape': 'failed to create document copy — could not add document context: could not write context scope binders: Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=', 'count': 5, 'error_class': 'neo4j', 'first_seen': 1794847742, 'sample': 'failed to create document copy — could not add document context: could not write context scope binders: Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=', 'trace': 'f91346437409440b0cc533d78b9297f2', 'shape_hash': '46565ad41f6336fc', 'window': [1794844504, 1794848104], 'count_is_floor': False, 'discriminator': '46565ad41f6336fc'}, 'evidence': [{'label': 'Errors, grouped', 'href': '/errors?cluster=master&from=1794844504&to=1794848104&service=execsvc'}, {'label': 'Logs', 'href': '/logs?cluster=master&from=1794844504&to=1794848104&service=execsvc&severity=ERROR'}, {'label': 'Example trace', 'href': '/trace/f91346437409440b0cc533d78b9297f2?cluster=master'}], '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': 60.0, 'status': 'open', 'first_seen': 1794848104, 'last_seen': 1794848104, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1, 'narrative': None, 'narrative_kind': None, 'discriminator': '46565ad41f6336fc', 'level': 'medium', 'told_level': None, 'episode_at': 1794848104, 'chat_thread': None, 'kind_label': 'Error never seen before', 'group': 'Errors', 'age_s': 134, 'stale_s': 134}
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 |