execsvc.auto-query-reeval-sweep: 7 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?
warning
Background job failing
delta
resolved
impact 42
opened 1d ago · last observed 1d ago · observed 17× · #17463 · 95e2e8acefd57597a3cd
What happened template
The background job execsvc.auto-query-reeval-sweep on delta failed 7 runs recently (99 failure lines; lines within one run count once), detected via its structured error/exception field (below ERROR severity). A job that logs its failures below ERROR severity — a WARNING carrying an error field — is invisible to the novel-shape detector and to the page's own failed count; this detector reads the error field itself, which is why the finding now appears. The sample failure is in the facts.
A named background job whose runs keep failing (error-severity bursts) in the last hour — volume, not novelty; the novel-shape detector only fires the first time.
The facts
| job | execsvc.auto-query-reeval-sweep |
| service | execsvc |
| failed_runs | 7 |
| error_lines | 99 |
| sample | no result from branch evaluation for branch, protocolId=77bcfccb-cc59-4aea-bff8-0991eaa0c788 activityRefId=d3ad124c-6a7b-419c-b01d-522c2c83e633 |
| error_signature | no result from branch evaluation for branch, protocolId=? activityRefId=? |
| failing_at | execution/activityV2.go:901 |
| trace | projects/tilda-trial-production/traces/12b1b031d6c085095ca6bffe1f46e43f |
| detected_via | structured error/exception field (below ERROR severity) |
| note | a run is a burst of lines that truly look like failures — an error/exception field, an error-worded message, or a failure status; lines within one burst count as one run. Lines a job dumps at ERROR that are neither (the steps that SUCCEEDED, banner rules) are ignored, so a service that logs its whole context on failure is not miscounted. `failing_at` is the call site those failures came from — for a coarse job (one set_job wrapping a pipeline) more specific than the job name. |
| discriminator | |
| window | 2026-11-17 03:39:50 UTC → 2026-11-17 09:39:50 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-17 03:39:50 UTC → 2026-11-17 09:39:50 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 |
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:22:34 UTCthis finding execsvc.auto-query-reeval-sweep: 7 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?
- 2026-11-16 18:39:47 UTCfinding · info execsvc: p95 latency (ms) 16.90 s — 37.9× the fleet's usual 446 ms (also p99 latency (ms) 1.6 min; Neo4j queries per request 76.9)
- 2026-11-16 18:54:59 UTCfinding · critical execsvc: a new error shape, 150× in the last hour, never seen in 90 days (no result from branch evaluation)
- 2026-11-16 19:00:00 UTClatency execsvc p95 peaked at 32.10 s
- 2026-11-16 19:14:41 UTCfinding · critical execsvc: a new error shape, 55× in the last hour, never seen in 90 days (evalResult is not a bool)
- 2026-11-17 09:00:00 UTCerrors execsvc 5xx peaked at 10 in one five-minute bucket (median 0 in this window)
- 2026-11-17 09:59:37 UTCfinding · critical execsvc: a new error shape, 9× in the last hour, never seen in 90 days (Request completed — ? · could not save Careplan activity V2)
History
- 2026-11-16 16:22:34 UTCopened x-ray · severity=warning title=execsvc.auto-query-reeval-sweep: 5 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=? finding={'id': 17463, 'fingerprint': '95e2e8acefd57597a3cd', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'delta', 'subject': 'execsvc.auto-query-reeval-sweep', 'title': 'execsvc.auto-query-reeval-sweep: 5 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?', 'facts': {'job': 'execsvc.auto-query-reeval-sweep', 'service': 'execsvc', 'failed_runs': 5, 'error_lines': 52, 'sample': 'no result from branch evaluation for branch, protocolId=77bcfccb-cc59-4aea-bff8-0991eaa0c788 activityRefId=04368312-d4bc-40b1-8ab5-300e55c0ce3a', 'error_signature': 'no result from branch evaluation for branch, protocolId=? activityRefId=?', 'failing_at': 'execution/activityV2.go:882', 'trace': 'projects/tilda-trial-production/traces/7bce6fd5fb57a5f7ec3d2edce7a8fdb0', 'detected_via': 'ERROR-severity log lines', 'window': [1794824554, 1794846154], 'note': 'a run is a burst of lines that truly look like failures — an error/exception field, an error-worded message, or a failure status; lines within one burst count as one run. Lines a job dumps at ERROR that are neither (the steps that SUCCEEDED, banner rules) are ignored, so a service that logs its whole context on failure is not miscounted. `failing_at` is the call site those failures came from — for a coarse job (one set_job wrapping a pipeline) more specific than the job name.', 'discriminator': ''}, 'evidence': [{'label': "This job's page", 'href': '/jobs/execsvc.auto-query-reeval-sweep?cluster=delta&from=1794824554&to=1794846154'}, {'label': 'Background jobs', 'href': '/jobs?cluster=delta&from=1794824554&to=1794846154'}, {'label': 'Its error logs', 'href': '/logs?cluster=delta&from=1794824554&to=1794846154&severity=ERROR&q=execsvc.auto-query-reeval-sweep'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-production/traces/7bce6fd5fb57a5f7ec3d2edce7a8fdb0?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': 'error-severity job lines from BigQuery, last hour, burst-grouped per job'}, 'impact': 36.3, 'status': 'open', 'first_seen': 1794846154, 'last_seen': 1794846154, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1, 'narrative': None, 'narrative_kind': None, 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794846154, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 28, 'stale_s': 28}
- 2026-11-17 10:40:41 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 17463, 'fingerprint': '95e2e8acefd57597a3cd', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'delta', 'subject': 'execsvc.auto-query-reeval-sweep', 'title': 'execsvc.auto-query-reeval-sweep: 7 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?', 'facts': {'job': 'execsvc.auto-query-reeval-sweep', 'service': 'execsvc', 'failed_runs': 7, 'error_lines': 99, 'sample': 'no result from branch evaluation for branch, protocolId=77bcfccb-cc59-4aea-bff8-0991eaa0c788 activityRefId=d3ad124c-6a7b-419c-b01d-522c2c83e633', 'error_signature': 'no result from branch evaluation for branch, protocolId=? activityRefId=?', 'failing_at': 'execution/activityV2.go:901', 'trace': 'projects/tilda-trial-production/traces/12b1b031d6c085095ca6bffe1f46e43f', 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794886790, 1794908390], 'note': 'a run is a burst of lines that truly look like failures — an error/exception field, an error-worded message, or a failure status; lines within one burst count as one run. Lines a job dumps at ERROR that are neither (the steps that SUCCEEDED, banner rules) are ignored, so a service that logs its whole context on failure is not miscounted. `failing_at` is the call site those failures came from — for a coarse job (one set_job wrapping a pipeline) more specific than the job name.', 'discriminator': ''}, 'evidence': [{'label': "This job's page", 'href': '/jobs/execsvc.auto-query-reeval-sweep?cluster=delta&from=1794886790&to=1794908390'}, {'label': 'Background jobs', 'href': '/jobs?cluster=delta&from=1794886790&to=1794908390'}, {'label': 'Its error logs', 'href': '/logs?cluster=delta&from=1794886790&to=1794908390&severity=ERROR&q=execsvc.auto-query-reeval-sweep'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-production/traces/12b1b031d6c085095ca6bffe1f46e43f?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': 'error-severity job lines from BigQuery, last hour, burst-grouped per job'}, 'impact': 41.9, 'status': 'resolved', 'first_seen': 1794846154, 'last_seen': 1794908390, 'resolved_at': 1794912041, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 17, 'narrative': "The background job execsvc.auto-query-reeval-sweep on delta failed 7 runs recently (99 failure lines; lines within one run count once), detected via its structured error/exception field (below ERROR severity). A job that logs its failures below ERROR severity — a WARNING carrying an error field — is invisible to the novel-shape detector and to the page's own failed count; this detector reads the error field itself, which is why the finding now appears. The sample failure is in the facts.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794846154, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 66013, 'stale_s': 3777}
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 | error-severity job lines from BigQuery, last hour, burst-grouped per job |
| detector | job_failing |