execsvc.auto-query-reeval-sweep: 11 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?
warning
Background job failing
production
open
impact 45
opened 1d ago · last observed 1d ago · observed 8× · #17498 · 1048e71d57e959ad49bf
What happened template
The background job execsvc.auto-query-reeval-sweep on production failed 11 runs recently (425 failure lines; lines within one run count once), detected via its ERROR-severity log lines. 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 | 11 |
| error_lines | 425 |
| 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:882 |
| trace | projects/tilda-trial-production/traces/98fde5cd0882405d5d4093c6c737f232 |
| detected_via | ERROR-severity log lines |
| 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 04:40:41 UTC → 2026-11-17 10:40:41 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 04:40:41 UTC → 2026-11-17 10:40:41 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-17 02:54:44 UTCthis finding execsvc.auto-query-reeval-sweep: 11 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?
- 2026-11-17 06:00:00 UTClatency execsvc p95 peaked at 2.30 s
History
- 2026-11-17 02:54:44 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': 17498, 'fingerprint': '1048e71d57e959ad49bf', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'production', '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': 416, 'sample': 'no result from branch evaluation for branch, protocolId=77bcfccb-cc59-4aea-bff8-0991eaa0c788 activityRefId=157c0866-dee2-4cd3-9a05-79e3b3d53dd0', 'error_signature': 'no result from branch evaluation for branch, protocolId=? activityRefId=?', 'failing_at': 'execution/activityV2.go:882', 'trace': 'projects/tilda-trial-production/traces/00f075f7d8cf22ef7f6219eef23a88cf', 'detected_via': 'ERROR-severity log lines', 'window': [1794862484, 1794884084], '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=production&from=1794862484&to=1794884084'}, {'label': 'Background jobs', 'href': '/jobs?cluster=production&from=1794862484&to=1794884084'}, {'label': 'Its error logs', 'href': '/logs?cluster=production&from=1794862484&to=1794884084&severity=ERROR&q=execsvc.auto-query-reeval-sweep'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-production/traces/00f075f7d8cf22ef7f6219eef23a88cf?cluster=production'}], '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': 'open', 'first_seen': 1794884084, 'last_seen': 1794884084, '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': 1794884084, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 41, 'stale_s': 41}
- 2026-11-17 07:35:33 UTCnotified x-ray · alert_id=11 channel=in-app status=delivered send_id=52049
- 2026-11-17 07:35:34 UTCnotified x-ray · alert_id=11 channel=prod-notifications status=sent send_id=52049
Notifications
- 2026-11-17 07:35:33 UTCopenedin-app · delivered
- 2026-11-17 07:35:31 UTCopenedprod-notifications · sent
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 |