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 16:06:35.
› →|
updated 2d 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.tilda-study-automation-regsvc-sub: 26 failed runs in the last 6 h — Plan definition not found for study ?

critical Background job failing automation open impact 50 opened 27d ago · last observed 2d ago · observed 447× · #5485 · d3291807318665c32ff7

What happened template

The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 26 runs recently (201 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

jobpubsub.tilda-study-automation-regsvc-sub
serviceregsvc
failed_runs26
error_lines201
samplePlan definition not found for study 5f590e14-d72f-49e5-a37b-e02af7a907f7
error_signaturePlan definition not found for study ?
failing_atpubsub/pubsub.go:747
traceprojects/tilda-trial-automation/traces/a917e57d264201327a970dae71b3dfea
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

What is failing in regsvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from regsvc. 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

2388× workflow not found since 2026-09-25 08:05:52 UTC
1032× workflow is already added to study since 2026-10-18 05:55:05 UTC
350× failed to get organization — object Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found since 2026-09-22 14:16:11 UTC
125× failed to process organization onboarding — user with email not found since 2026-10-21 00:13:05 UTC
121× failed to add workflows to study — Plan definition not found for study 496f314a-0ca6-4472-9cd4-34061d5ce9f2 since 2026-10-18 05:40:59 UTC

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

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

History

  • 2026-11-14 12:52:44 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 5 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 5, 'error_lines': 116, 'sample': 'Plan definition not found for study 41672d24-a0e2-4150-867e-9f4a53d4271f', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'pubsublib/googlepubsub.go:700', 'trace': 'projects/tilda-trial-automation/traces/e2e7e5738b186a35c4c2e0c6d8a68ccd', 'detected_via': 'ERROR-severity log lines', 'window': [1794635534, 1794657134], '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.tilda-study-automation-regsvc-sub?cluster=automation&from=1794635534&to=1794657134'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794635534&to=1794657134'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794635534&to=1794657134&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e5738b186a35c4c2e0c6d8a68ccd?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': 31.1, 'status': 'resolved', 'first_seen': 1792762426, 'last_seen': 1794657134, 'resolved_at': 1794660764, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 392, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 5 runs recently (116 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': 1794540161, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 1898375, 'stale_s': 3667}
  • 2026-11-14 21:19:28 UTCreopened x-ray · severity=warning was=warning title=pubsub.tilda-study-automation-regsvc-sub: 9 failed runs in the last 6 h — Plan definition not found for study ? level=medium was_level=medium finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 9 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 9, 'error_lines': 40, 'sample': 'Plan definition not found for study 14da8e77-d6ec-478d-b43c-3fe01ed55589', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'pubsublib/googlepubsub.go:697', 'trace': 'projects/tilda-trial-automation/traces/a917e5737cd6d3f27a970daccd91500a', 'detected_via': 'ERROR-severity log lines', 'window': [1794669568, 1794691168], '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.tilda-study-automation-regsvc-sub?cluster=automation&from=1794669568&to=1794691168'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794669568&to=1794691168'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794669568&to=1794691168&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e5737cd6d3f27a970daccd91500a?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.1, 'status': 'open', 'first_seen': 1792762426, 'last_seen': 1794691168, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 393, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 5 runs recently (116 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': 1794691168, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 1928779, 'stale_s': 37}
  • 2026-11-14 23:23:36 UTCescalated x-ray · severity=warning was=warning title=pubsub.tilda-study-automation-regsvc-sub: 21 failed runs in the last 6 h — Plan definition not found for study ? level=high was_level=medium finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 21 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 21, 'error_lines': 134, 'sample': 'Plan definition not found for study 4690ee28-652b-4863-a0cd-a68bfb01202a', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'workflow/workflow.go:1373', 'trace': 'projects/tilda-trial-automation/traces/a917e5737cd6d3f0a0da79800c0ccb9a', 'detected_via': 'ERROR-severity log lines', 'window': [1794677016, 1794698616], '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.tilda-study-automation-regsvc-sub?cluster=automation&from=1794677016&to=1794698616'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794677016&to=1794698616'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794677016&to=1794698616&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e5737cd6d3f0a0da79800c0ccb9a?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.1, 'status': 'open', 'first_seen': 1792762426, 'last_seen': 1794698616, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 395, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 15 runs recently (98 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': None, 'episode_at': 1794691168, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 1936232, 'stale_s': 42}
  • 2026-11-15 00:25:54 UTCescalated x-ray · severity=critical was=warning title=pubsub.tilda-study-automation-regsvc-sub: 26 failed runs in the last 6 h — Plan definition not found for study ? level=high was_level=high finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'critical', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 26 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 26, 'error_lines': 164, 'sample': 'Plan definition not found for study 14da8e77-d6ec-478d-b43c-3fe01ed55589', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'pubsublib/googlepubsub.go:697', 'trace': 'projects/tilda-trial-automation/traces/a917e5737cd6d3f27a970daccd91500a', 'detected_via': 'ERROR-severity log lines', 'window': [1794680754, 1794702354], '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.tilda-study-automation-regsvc-sub?cluster=automation&from=1794680754&to=1794702354'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794680754&to=1794702354'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794680754&to=1794702354&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e5737cd6d3f27a970daccd91500a?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': 45.6, 'status': 'open', 'first_seen': 1792762426, 'last_seen': 1794702354, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 396, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 21 runs recently (134 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': None, 'episode_at': 1794691168, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 1939971, 'stale_s': 43}
  • 2026-11-16 19:33:28 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 6 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 6, 'error_lines': 170, 'sample': 'Plan definition not found for study 5eb6f902-5f40-4674-8e15-814fd8c36f96', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'workflow/workflow.go:1373', 'trace': 'projects/tilda-trial-automation/traces/a917e57cc2f016a5fac5803769b405d7', 'detected_via': 'ERROR-severity log lines', 'window': [1794832329, 1794853929], '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.tilda-study-automation-regsvc-sub?cluster=automation&from=1794832329&to=1794853929'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794832329&to=1794853929'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794832329&to=1794853929&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e57cc2f016a5fac5803769b405d7?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': 31.0, 'status': 'resolved', 'first_seen': 1792762426, 'last_seen': 1794853929, 'resolved_at': 1794857608, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 434, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 6 runs recently (170 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': 1794691168, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2095224, 'stale_s': 3721}
  • 2026-11-16 21:38:50 UTCreopened x-ray · severity=warning was=warning title=pubsub.tilda-study-automation-regsvc-sub: 7 failed runs in the last 6 h — Plan definition not found for study ? level=medium was_level=medium finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 7 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 7, 'error_lines': 188, 'sample': 'Plan definition not found for study 5f9207d6-a44f-4112-823b-55889b69d774', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'pubsublib/googlepubsub.go:697', 'trace': 'projects/tilda-trial-automation/traces/e2e7e573b27ea45b993b31aa5585d56e', '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/pubsub.tilda-study-automation-regsvc-sub?cluster=automation&from=1794843530&to=1794865130'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794843530&to=1794865130'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794843530&to=1794865130&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e573b27ea45b993b31aa5585d56e?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': 1792762426, 'last_seen': 1794865130, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 435, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 6 runs recently (170 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': 1794865130, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2102753, 'stale_s': 49}
  • 2026-11-16 23:44:07 UTCescalated x-ray · severity=warning was=warning title=pubsub.tilda-study-automation-regsvc-sub: 20 failed runs in the last 6 h — Plan definition not found for study ? level=high was_level=medium finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 20 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 20, 'error_lines': 263, 'sample': 'Plan definition not found for study d3f9d6f0-0719-4650-b0e4-d1c5977b2b4d', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'pubsublib/googlepubsub.go:697', 'trace': 'projects/tilda-trial-automation/traces/a917e5733d23a3427a970dab7110b475', '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/pubsub.tilda-study-automation-regsvc-sub?cluster=automation&from=1794851047&to=1794872647'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794851047&to=1794872647'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794851047&to=1794872647&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e5733d23a3427a970dab7110b475?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': 1792762426, 'last_seen': 1794872647, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 437, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 14 runs recently (227 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': None, 'episode_at': 1794865130, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2110251, 'stale_s': 30}
  • 2026-11-17 00:48:04 UTCescalated x-ray · severity=critical was=warning title=pubsub.tilda-study-automation-regsvc-sub: 27 failed runs in the last 6 h — Plan definition not found for study ? level=high was_level=high finding={'id': 5485, 'fingerprint': 'd3291807318665c32ff7', 'kind': 'job.failing', 'severity': 'critical', 'cluster': 'automation', 'subject': 'pubsub.tilda-study-automation-regsvc-sub', 'title': 'pubsub.tilda-study-automation-regsvc-sub: 27 failed runs in the last 6 h — Plan definition not found for study ?', 'facts': {'job': 'pubsub.tilda-study-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 27, 'error_lines': 296, 'sample': 'Plan definition not found for study d3f9d6f0-0719-4650-b0e4-d1c5977b2b4d', 'error_signature': 'Plan definition not found for study ?', 'failing_at': 'pubsublib/googlepubsub.go:697', 'trace': 'projects/tilda-trial-automation/traces/a917e5733d23a3427a970dab7110b475', 'detected_via': 'ERROR-severity log lines', 'window': [1794854884, 1794876484], '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.tilda-study-automation-regsvc-sub?cluster=automation&from=1794854884&to=1794876484'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794854884&to=1794876484'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794854884&to=1794876484&severity=ERROR&q=pubsub.tilda-study-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e5733d23a3427a970dab7110b475?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': 45.5, 'status': 'open', 'first_seen': 1792762426, 'last_seen': 1794876484, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 438, 'narrative': "The background job pubsub.tilda-study-automation-regsvc-sub on automation failed 20 runs recently (263 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': None, 'episode_at': 1794865130, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 2114094, 'stale_s': 36}

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