Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 7 days▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 13:37:39.
› →|
updated 1d ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.
← findings

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)

critical Error never seen before master open impact 58 Owner: Madhava Mukkamala (backup: Shashank Agrawal) opened 1d ago · last observed 1d ago · observed 3× · #17471 · f7abac559f1b83a9613c

What happened template

execsvc logged “failed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=?, clientId=?] can't acquire Excl” 5 times in the last hour and never before in 90 days on master (first seen 2026-11-16 16:49 UTC, raised at tildadb/util.go:1004). 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 hit a burst of Neo4j DeadlockDetected errors, all at 16:49 UTC: 5× 'failed to run cypher in transaction' (tildadb/util.go:1004), plus 14× util.go:993, 12× bulk-write (doclib/createDocument.go:1015), 12+5× document copy (doclib/copyDocument.go:74) and 5× scope binders (doclib/context.go:335).
The errors have not recurred since then (last seen 16:49 per error lines).
The 5 deploys in the prior 24 h were config-only autosync; the closest was 15:39 (69 min before), with no image or commit change and nothing tying it to these files.
The util.go:993 deadlock shape has existed since 2026-11-15, so deadlocks are not new; what is new is the document-copy write path hitting them.
Next step: open the example trace and check which concurrent document copies (bulk doc write vs. context scope binders) took ExclusiveLocks on the same nodes, then confirm the copy path retries on TransientError.

low confidence

claude-opus-5-5 · 1d ago · $0.05 — every link above is evidence it read; nothing else was claimed.

The facts

serviceexecsvc
callertildadb/util.go:1004
shapefailed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=?, clientId=?] can't acquire ExclusiveLock{owner=ForsetiClient
count5
error_classneo4j
first_seen2026-11-16 16:49:02 UTC (1d ago)
samplefailed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=2457665, clientId=4383] can't acquire ExclusiveLock{owner=ForsetiClient
tracef91346437409440b0cc533d78b9297f2
shape_hash40cb59447bef57df
count_is_floorno
discriminator40cb59447bef57df
window2026-11-16 16:34:53 UTC → 2026-11-16 17:34:53 UTC

What is failing in execsvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from execsvc. In this finding's window (2026-11-16 16:34:53 UTC → 2026-11-16 17:34:53 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

21× error anchor visit index has not been set. Does this study have an anchor visit? continuing without setting day/date ran… since 2026-11-06 00:02:19 UTC
12× error anchor visit index has not been set. Does this study have an anchor visit? continuing without setting day/date ran… since 2026-11-12 15:37:28 UTC

All execsvc errors, grouped → · service page · its logs

The story — No execsvc deploy or hand change is recorded in the hour before this opened. Everything below is execsvc only.

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 run cypher in transaction — Neo4jError: Neo.TransientError.T) finding={'id': 17471, 'fingerprint': 'f7abac559f1b83a9613c', '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 run cypher in transaction — Neo4jError: Neo.TransientError.T)', 'facts': {'service': 'execsvc', 'caller': 'tildadb/util.go:1004', 'shape': "failed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=?, clientId=?] can't acquire ExclusiveLock{owner=ForsetiClient", 'count': 5, 'error_class': 'neo4j', 'first_seen': 1794847742, 'sample': "failed to run cypher in transaction — Neo4jError: Neo.TransientError.Transaction.DeadlockDetected (ForsetiClient[transactionId=2457665, clientId=4383] can't acquire ExclusiveLock{owner=ForsetiClient", 'trace': 'f91346437409440b0cc533d78b9297f2', 'shape_hash': '40cb59447bef57df', 'window': [1794844504, 1794848104], 'count_is_floor': False, 'discriminator': '40cb59447bef57df'}, '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': '40cb59447bef57df', '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

sourcelive
collected_atNone
age_secondsNone
staleFalse
shownNone
totalNone
truncatedFalse
coverage_fromNone
retain_daysNone
noteCloud Logging, last hour, grouped by (service, caller, shape)
detectorerrors_novel