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 05:32:48.
› →|
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

workplan.workplan_config: 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 31 opened 30d ago · last observed 1d ago · observed 158× · #5063 · e8577e15dcb9cc20f2bb

What happened template

The background job workplan.workplan_config on automation failed 12 runs recently (75 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

jobworkplan.workplan_config
serviceworkplan-agent
failed_runs12
error_lines75
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_atworker/pubsub_manager.py:357
traceprojects/tilda-trial-automation/traces/e2e7e57aea16389d0f1c793df92e28a2
detected_viaERROR-severity log lines
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

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

History

  • 2026-11-16 11:36:11 UTCreopened x-ray · severity=warning was=warning title=workplan.workplan_config: 6 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': 5063, 'fingerprint': 'e8577e15dcb9cc20f2bb', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'workplan.workplan_config', 'title': 'workplan.workplan_config: 6 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': 'workplan.workplan_config', 'service': 'workplan-agent', 'failed_runs': 6, 'error_lines': 30, 'sample': 'A listed condition would be lost: milestone 091504af-370e-471e-8487-52c9a9f10c85 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': 'handlers/workplan_cfg_handler.py:185', 'trace': 'projects/tilda-trial-automation/traces/e2e7e5789a53701eb20b6b05612aa406', 'detected_via': 'ERROR-severity log lines', '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/workplan.workplan_config?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=workplan.workplan_config'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e5789a53701eb20b6b05612aa406?cluster=automation'}], '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.0, 'status': 'open', 'first_seen': 1792470571, 'last_seen': 1794828971, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 151, 'narrative': "The background job workplan.workplan_config on automation failed 5 runs recently (45 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': None, 'episode_at': 1794828971, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2358563, 'stale_s': 163}

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