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:34:18.
› →|
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.onboarding-automation-regsvc-sub: 6 failed runs in the last 6 h — object Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found

warning Background job failing automation resolved impact 31 opened 72d ago · last observed 2d ago · observed 88× · #1005 · 6664e031fed014423640

What happened template

The background job pubsub.onboarding-automation-regsvc-sub on automation failed 6 runs recently (28 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.onboarding-automation-regsvc-sub
serviceregsvc
failed_runs6
error_lines28
sampleobject Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found
error_signatureobject Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found
failing_atpubsub/pubsub.go:128
traceprojects/tilda-trial-automation/traces/93151ae97c754b444c655e0bdb037358
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-16 09:18:05 UTC → 2026-11-16 15:18:05 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-16 09:18:05 UTC → 2026-11-16 15:18:05 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-16 12:58:26 UTCreopened x-ray · severity=warning was=warning title=pubsub.onboarding-automation-regsvc-sub: 6 failed runs in the last 6 h — failed to publish workflow: Error from API call: status: ?, response { ?: ? } level=medium was_level=medium finding={'id': 1005, 'fingerprint': '6664e031fed014423640', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.onboarding-automation-regsvc-sub', 'title': 'pubsub.onboarding-automation-regsvc-sub: 6 failed runs in the last 6 h — failed to publish workflow: Error from API call: status: ?, response { ?: ? }', 'facts': {'job': 'pubsub.onboarding-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 6, 'error_lines': 82, 'sample': 'failed to publish workflow: Error from API call: status: 403, response {\n "message": "user with email not found"\n}\n', 'error_signature': 'failed to publish workflow: Error from API call: status: ?, response { ?: ? }', 'failing_at': 'pubsublib/googlepubsub.go:700', 'trace': 'projects/tilda-trial-automation/traces/e2e7e577c95c44f6d592776898dabdac', 'detected_via': 'ERROR-severity log lines', 'window': [1794812306, 1794833906], '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.onboarding-automation-regsvc-sub?cluster=automation&from=1794812306&to=1794833906'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794812306&to=1794833906'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794812306&to=1794833906&severity=ERROR&q=pubsub.onboarding-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e577c95c44f6d592776898dabdac?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': 1788772902, 'last_seen': 1794833906, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 86, 'narrative': "The background job pubsub.onboarding-automation-regsvc-sub on automation failed 8 runs recently (21 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': 1794833906, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6061054, 'stale_s': 50}
  • 2026-11-16 16:22:34 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 1005, 'fingerprint': '6664e031fed014423640', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'pubsub.onboarding-automation-regsvc-sub', 'title': 'pubsub.onboarding-automation-regsvc-sub: 6 failed runs in the last 6 h — object Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found', 'facts': {'job': 'pubsub.onboarding-automation-regsvc-sub', 'service': 'regsvc', 'failed_runs': 6, 'error_lines': 28, 'sample': 'object Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found', 'error_signature': 'object Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found', 'failing_at': 'pubsub/pubsub.go:128', 'trace': 'projects/tilda-trial-automation/traces/93151ae97c754b444c655e0bdb037358', 'detected_via': 'ERROR-severity log lines', '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.onboarding-automation-regsvc-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.onboarding-automation-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/93151ae97c754b444c655e0bdb037358?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': 1788772902, 'last_seen': 1794842285, 'resolved_at': 1794846154, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 88, 'narrative': "The background job pubsub.onboarding-automation-regsvc-sub on automation failed 6 runs recently (28 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': 1794833906, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6073279, 'stale_s': 3896}

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