Xray
1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 1 hour▾
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-20 03:46:32.
› →|
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

pubsub.workplan-config-response-automation-workplansvc-sub: 12 failed runs in the last 6 h — A listed condition would be lost: milestone ? has ? review or checkpoint steps, so the decision it n

warning Background job failing automation open impact 32 opened 29d ago · last observed 1d ago · observed 160× · #5062 · 10f0601682aa2f9965b9

What happened template

The background job pubsub.workplan-config-response-automation-workplansvc-sub on automation failed 12 runs recently (15 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

jobpubsub.workplan-config-response-automation-workplansvc-sub
serviceworkplansvc
failed_runs12
error_lines15
sampleA listed condition would be lost: milestone 760bd4c4-e803-42b5-bd3a-777a0a2a5e69 has 2 review or checkpoint steps, so the decision it names cannot be bound
error_signatureA listed condition would be lost: milestone ? has ? review or checkpoint steps, so the decision it names cannot be bound
failing_atpubsub/pubsub.go:783
trace—
detected_viastructured error/exception field (below ERROR severity)
notea 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
window2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC

What is failing in workplansvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from workplansvc. In this finding's window (2026-11-17 04:40:41 UTC → 2026-11-17 10:40:41 UTC) there were 10; every line links to the grouped errors behind it.

POST /api/workplan/configs 4 bad of 66 calls · 40% of the service's 5xx
DELETE /api/workplan/templates/:id 2 bad of 4 calls · 20% of the service's 5xx
POST /api/workplan/templates 2 bad of 87 calls · 20% of the service's 5xx
POST /api/workplan/types 2 bad of 100 calls · 20% of the service's 5xx

The error shapes behind them

132× Failed to create workplan config — site 3aab23db-d69f-4946-b743-2613d2dccfef not found since 2026-10-20 01:14:02 UTC
8× work plan template name cannot be empty since 2026-09-15 01:46:21 UTC
8× Request completed — 500 · work plan template name cannot be empty since 2026-09-25 09:27:33 UTC
8× Request completed — 500 · could not create work plan type:work plan type name cannot be empty since 2026-09-25 09:21:59 UTC
8× could not create work plan type:work plan type name cannot be empty since 2026-09-15 01:41:21 UTC

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

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

History

  • 2026-11-16 11:36:11 UTCreopened x-ray · severity=warning was=warning title=pubsub.workplan-config-response-automation-workplansvc-sub: 6 failed runs in the last 6 h — Either object does not exist OR object has been updated since last read level=medium was_level=medium finding={'id': 5062, 'fingerprint': '10f0601682aa2f9965b9', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.workplan-config-response-automation-workplansvc-sub', 'title': 'pubsub.workplan-config-response-automation-workplansvc-sub: 6 failed runs in the last 6 h — Either object does not exist OR object has been updated since last read', 'facts': {'job': 'pubsub.workplan-config-response-automation-workplansvc-sub', 'service': 'workplansvc', 'failed_runs': 6, 'error_lines': 7, 'sample': 'Either object does not exist OR object has been updated since last read', 'error_signature': 'Either object does not exist OR object has been updated since last read', 'failing_at': 'pubsub/pubsub.go:783', 'trace': None, 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794807371, 1794828971], '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/pubsub.workplan-config-response-automation-workplansvc-sub?cluster=automation&from=1794807371&to=1794828971'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794807371&to=1794828971'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794807371&to=1794828971&severity=ERROR&q=pubsub.workplan-config-response-automation-workplansvc-sub'}], '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': 26.4, 'status': 'open', 'first_seen': 1792470571, 'last_seen': 1794828971, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 153, 'narrative': "The background job pubsub.workplan-config-response-automation-workplansvc-sub on automation failed 6 runs recently (9 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': 1794828971, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2358563, 'stale_s': 163}
  • 2026-11-16 16:22:34 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 5062, 'fingerprint': '10f0601682aa2f9965b9', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.workplan-config-response-automation-workplansvc-sub', 'title': 'pubsub.workplan-config-response-automation-workplansvc-sub: 7 failed runs in the last 6 h — Either object does not exist OR object has been updated since last read', 'facts': {'job': 'pubsub.workplan-config-response-automation-workplansvc-sub', 'service': 'workplansvc', 'failed_runs': 7, 'error_lines': 8, 'sample': 'Either object does not exist OR object has been updated since last read', 'error_signature': 'Either object does not exist OR object has been updated since last read', 'failing_at': 'pubsub/pubsub.go:783', 'trace': None, 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794820685, 1794842285], '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/pubsub.workplan-config-response-automation-workplansvc-sub?cluster=automation&from=1794820685&to=1794842285'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794820685&to=1794842285'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794820685&to=1794842285&severity=ERROR&q=pubsub.workplan-config-response-automation-workplansvc-sub'}], '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': 31.5, 'status': 'resolved', 'first_seen': 1792470571, 'last_seen': 1794842285, 'resolved_at': 1794846154, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 156, 'narrative': "The background job pubsub.workplan-config-response-automation-workplansvc-sub on automation failed 7 runs recently (8 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': 1794828971, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2375610, 'stale_s': 3896}
  • 2026-11-17 07:24:09 UTCreopened x-ray · severity=warning was=warning title=pubsub.workplan-config-response-automation-workplansvc-sub: 5 failed runs in the last 6 h — A listed condition would be lost: milestone ? has ? review or checkpoint steps, so the decision it n level=medium was_level=medium finding={'id': 5062, 'fingerprint': '10f0601682aa2f9965b9', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.workplan-config-response-automation-workplansvc-sub', 'title': 'pubsub.workplan-config-response-automation-workplansvc-sub: 5 failed runs in the last 6 h — A listed condition would be lost: milestone ? has ? review or checkpoint steps, so the decision it n', 'facts': {'job': 'pubsub.workplan-config-response-automation-workplansvc-sub', 'service': 'workplansvc', 'failed_runs': 5, 'error_lines': 6, 'sample': 'A listed condition would be lost: milestone 526e6d3f-4555-4e88-a4cf-9392162b8021 has 2 review or checkpoint steps, so the decision it names cannot be bound', 'error_signature': 'A listed condition would be lost: milestone ? has ? review or checkpoint steps, so the decision it names cannot be bound', 'failing_at': 'pubsub/pubsub.go:783', 'trace': None, 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794878649, 1794900249], '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/pubsub.workplan-config-response-automation-workplansvc-sub?cluster=automation&from=1794878649&to=1794900249'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794878649&to=1794900249'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794878649&to=1794900249&severity=ERROR&q=pubsub.workplan-config-response-automation-workplansvc-sub'}], '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': 26.5, 'status': 'open', 'first_seen': 1792470571, 'last_seen': 1794900249, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 157, 'narrative': "The background job pubsub.workplan-config-response-automation-workplansvc-sub on automation failed 7 runs recently (8 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': 1794900249, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2429763, 'stale_s': 85}

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
noteerror-severity job lines from BigQuery, last hour, burst-grouped per job
detectorjob_failing