execsvc.auto-query-reeval: 6 failed runs in the last 6 h — participant activity ?: auto query ? on question ?: no result from branch evaluation for branch, pro
warning
Background job failing
production
resolved
impact 47
opened 1d ago · last observed 1d ago · observed 7× · #17487 · 4f9a7e43991dea9318ad
What happened template
The background job execsvc.auto-query-reeval on production failed 6 runs recently (25 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 |
| service | execsvc |
| failed_runs | 6 |
| error_lines | 25 |
| sample | participant activity 0294d67b-775d-4580-a46a-4b3085691136: auto query cee26d92-2b6c-4e45-a32f-b8758d9ff83a on question 522e2ac3-5aeb-4dd4-ac75-a4fc48384c13: no result from branch evaluation for branch, protocolId=77bcfccb-cc59-4aea-bff8-0991eaa0c788 activityRefId=5412851c-a89c-46a3-a3e1-dd026f0ea12f |
| error_signature | participant activity ?: auto query ? on question ?: no result from branch evaluation for branch, protocolId=? activityRe |
| failing_at | execution/activityV2.go:882 |
| trace | projects/tilda-trial-production/traces/b4a46af1511b00609ba4b32b4050ff0c |
| 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-16 22:00:15 UTC → 2026-11-17 04:00:15 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 22:00:15 UTC → 2026-11-17 04:00:15 UTC) there were 0; every line links to the grouped errors behind it.
The error shapes behind them
| 473× | no result from branch evaluation since 2026-11-11 14:55:54 UTC |
| 473× | failed to evaluate and raise auto query for participant question — no result from branch evaluation for branch, protocol… since 2026-11-16 16:26:25 UTC |
| 78× | failed to evaluate and raise auto query for participant question — evalResult is not a bool since 2026-11-16 16:26:23 UTC |
| 78× | evalResult is not a bool since 2026-11-16 16:26:23 UTC |
| 2× | auto query re-evaluation failed — participant activity 0f6679fd-b9f6-4d32-b5ff-49e3b8f61e44: auto query 2010ccf4-d76a-4e… since 2026-11-16 17:47:43 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 20:00:00 UTClatency execsvc p95 peaked at 4.11 s
- 2026-11-16 20:38:50 UTCcypher execsvc shape 6966AB0B p95 went 98 ms → 190 ms across the window (122 runs)
- 2026-11-16 21:38:50 UTCthis finding execsvc.auto-query-reeval: 6 failed runs in the last 6 h — participant activity ?: auto query ? on question ?: no result from branch evaluation for branch, pro
History
- 2026-11-16 21:38:50 UTCopened x-ray · severity=warning title=execsvc.auto-query-reeval: 9 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=? finding={'id': 17487, 'fingerprint': '4f9a7e43991dea9318ad', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'production', 'subject': 'execsvc.auto-query-reeval', 'title': 'execsvc.auto-query-reeval: 9 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?', 'facts': {'job': 'execsvc.auto-query-reeval', 'service': 'execsvc', 'failed_runs': 9, 'error_lines': 830, '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/b4a46af1511b00609ba4b32b4050ff0c', 'detected_via': 'ERROR-severity log lines', 'window': [1794843530, 1794865130], '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?cluster=production&from=1794843530&to=1794865130'}, {'label': 'Background jobs', 'href': '/jobs?cluster=production&from=1794843530&to=1794865130'}, {'label': 'Its error logs', 'href': '/logs?cluster=production&from=1794843530&to=1794865130&severity=ERROR&q=execsvc.auto-query-reeval'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-production/traces/b4a46af1511b00609ba4b32b4050ff0c?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.5, 'status': 'open', 'first_seen': 1794865130, 'last_seen': 1794865130, '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': 1794865130, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 50, 'stale_s': 50}
- 2026-11-16 23:34:32 UTCnotified x-ray · alert_id=11 channel=in-app status=delivered send_id=51936
- 2026-11-16 23:34:34 UTCnotified x-ray · alert_id=11 channel=prod-notifications status=sent send_id=51936
- 2026-11-16 23:44:07 UTCescalated x-ray · severity=warning was=warning title=execsvc.auto-query-reeval: 20 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=? level=high was_level=medium finding={'id': 17487, 'fingerprint': '4f9a7e43991dea9318ad', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'production', 'subject': 'execsvc.auto-query-reeval', 'title': 'execsvc.auto-query-reeval: 20 failed runs in the last 6 h — no result from branch evaluation for branch, protocolId=? activityRefId=?', 'facts': {'job': 'execsvc.auto-query-reeval', 'service': 'execsvc', 'failed_runs': 20, 'error_lines': 347, '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/b4a46af1511b00609ba4b32b4050ff0c', 'detected_via': 'ERROR-severity log lines', 'window': [1794851047, 1794872647], '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?cluster=production&from=1794851047&to=1794872647'}, {'label': 'Background jobs', 'href': '/jobs?cluster=production&from=1794851047&to=1794872647'}, {'label': 'Its error logs', 'href': '/logs?cluster=production&from=1794851047&to=1794872647&severity=ERROR&q=execsvc.auto-query-reeval'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-production/traces/b4a46af1511b00609ba4b32b4050ff0c?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.7, 'status': 'open', 'first_seen': 1794865130, 'last_seen': 1794872647, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 3, 'narrative': "The background job execsvc.auto-query-reeval on production failed 16 runs recently (533 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.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'high', 'told_level': 'medium', 'episode_at': 1794865130, 'chat_thread': 'xray-alert-11-748fd5a928-4f9a7e43991dea9318ad-1794872072', 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 7548, 'stale_s': 31}
- 2026-11-17 01:29:53 UTCnotified x-ray · alert_id=10 channel=in-app status=delivered send_id=51953
- 2026-11-17 01:29:54 UTCnotified x-ray · alert_id=10 channel=prod-notifications status=sent send_id=51953
- 2026-11-17 05:00:47 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 17487, 'fingerprint': '4f9a7e43991dea9318ad', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'production', 'subject': 'execsvc.auto-query-reeval', 'title': 'execsvc.auto-query-reeval: 6 failed runs in the last 6 h — participant activity ?: auto query ? on question ?: no result from branch evaluation for branch, pro', 'facts': {'job': 'execsvc.auto-query-reeval', 'service': 'execsvc', 'failed_runs': 6, 'error_lines': 25, 'sample': 'participant activity 0294d67b-775d-4580-a46a-4b3085691136: auto query cee26d92-2b6c-4e45-a32f-b8758d9ff83a on question 522e2ac3-5aeb-4dd4-ac75-a4fc48384c13: no result from branch evaluation for branch, protocolId=77bcfccb-cc59-4aea-bff8-0991eaa0c788 activityRefId=5412851c-a89c-46a3-a3e1-dd026f0ea12f', 'error_signature': 'participant activity ?: auto query ? on question ?: no result from branch evaluation for branch, protocolId=? activityRe', 'failing_at': 'execution/activityV2.go:882', 'trace': 'projects/tilda-trial-production/traces/b4a46af1511b00609ba4b32b4050ff0c', 'detected_via': 'ERROR-severity log lines', 'window': [1794866415, 1794888015], '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?cluster=production&from=1794866415&to=1794888015'}, {'label': 'Background jobs', 'href': '/jobs?cluster=production&from=1794866415&to=1794888015'}, {'label': 'Its error logs', 'href': '/logs?cluster=production&from=1794866415&to=1794888015&severity=ERROR&q=execsvc.auto-query-reeval'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-production/traces/b4a46af1511b00609ba4b32b4050ff0c?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': 47.0, 'status': 'resolved', 'first_seen': 1794865130, 'last_seen': 1794888015, 'resolved_at': 1794891647, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 7, 'narrative': "The background job execsvc.auto-query-reeval on production failed 6 runs recently (25 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.", 'narrative_kind': 'template', 'discriminator': '', 'level': 'medium', 'told_level': 'high', 'episode_at': 1794865130, 'chat_thread': 'xray-alert-10-748fd5a928-4f9a7e43991dea9318ad-1794878993', 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 26612, 'stale_s': 3727}
- 2026-11-17 05:30:00 UTCnotified x-ray · alert_id=10 channel=in-app status=delivered send_id=52018
- 2026-11-17 05:30:01 UTCnotified x-ray · alert_id=10 channel=prod-notifications status=sent send_id=52018
- 2026-11-17 07:35:31 UTCnotified x-ray · alert_id=11 channel=in-app status=delivered send_id=52047
- 2026-11-17 07:35:33 UTCnotified x-ray · alert_id=11 channel=prod-notifications status=sent send_id=52047
Notifications
- 2026-11-17 07:35:31 UTCresolvedin-app · delivered
- 2026-11-17 07:35:31 UTCresolvedprod-notifications · sent
- 2026-11-17 05:30:00 UTCresolvedin-app · delivered
- 2026-11-17 05:30:00 UTCresolvedprod-notifications · sent
- 2026-11-17 01:29:53 UTCescalatedin-app · delivered
- 2026-11-17 01:29:53 UTCescalatedprod-notifications · sent
- 2026-11-16 23:34:32 UTCopenedin-app · delivered
- 2026-11-16 23:34:32 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 |