pubsub.onboarding-test27-regsvc-sub: 19 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A
warning
Background job failing
test27
open
impact 25
opened 16d ago · last observed 1d ago · observed 22× · #15295 · ce4bded218033c85b7c2
What happened template
The background job pubsub.onboarding-test27-regsvc-sub on test27 failed 19 runs recently (528 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 | pubsub.onboarding-test27-regsvc-sub |
| service | regsvc |
| failed_runs | 19 |
| error_lines | 528 |
| sample | failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: 401, response { "message": "Unauthorized: token expired" } |
| error_signature | failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: ?, |
| failing_at | pubsub/pubsub.go:151 |
| trace | projects/tilda-trial-dev/traces/a917e575a619912e495d8aca94537024 |
| 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-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
| 11296× | workflow not found since 2026-10-22 09:22:32 UTC |
| 1071× | failed to process organization onboarding — Unauthorized: token expired since 2026-11-02 06:22:22 UTC |
| 8× | failed to get organization — object Organization {deltimestamp:$a_deltimestamp,alias:$a_alias} not found since 2026-10-02 06:41:45 UTC |
The story — No regsvc deploy or hand change is recorded in the hour before this opened. Everything below is regsvc only.
- 2026-11-02 09:10:39 UTCthis finding pubsub.onboarding-test27-regsvc-sub: 19 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A
- 2026-11-14 01:12:42 UTCfinding · warning regsvc (tilda) image pull failing for at least 117 min — 1 pod
- 2026-11-17 00:00:00 UTClatency regsvc p95 peaked at 4.25 s
History
- 2026-11-16 11:36:11 UTCreopened x-ray · severity=warning was=warning title=pubsub.onboarding-test27-regsvc-sub: 5 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A level=medium was_level=medium finding={'id': 15295, 'fingerprint': 'ce4bded218033c85b7c2', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'test27', 'subject': 'pubsub.onboarding-test27-regsvc-sub', 'title': 'pubsub.onboarding-test27-regsvc-sub: 5 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A', 'facts': {'job': 'pubsub.onboarding-test27-regsvc-sub', 'service': 'regsvc', 'failed_runs': 5, 'error_lines': 1934, 'sample': 'failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: 401, response {\n "message": "Unauthorized: token expired"\n}\n', 'error_signature': 'failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: ?,', 'failing_at': 'pubsub/pubsub.go:151', 'trace': 'projects/tilda-trial-dev/traces/a917e57c2be767118ea8c2b8753c43ea', '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.onboarding-test27-regsvc-sub?cluster=test27&from=1794807371&to=1794828971'}, {'label': 'Background jobs', 'href': '/jobs?cluster=test27&from=1794807371&to=1794828971'}, {'label': 'Its error logs', 'href': '/logs?cluster=test27&from=1794807371&to=1794828971&severity=ERROR&q=pubsub.onboarding-test27-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-dev/traces/a917e57c2be767118ea8c2b8753c43ea?cluster=test27'}], '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': 20.0, 'status': 'open', 'first_seen': 1793610639, 'last_seen': 1794828971, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 5, 'narrative': "The background job pubsub.onboarding-test27-regsvc-sub on test27 failed 5 runs recently (18 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': 1218498, 'stale_s': 166}
- 2026-11-16 12:58:26 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 15295, 'fingerprint': 'ce4bded218033c85b7c2', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'test27', 'subject': 'pubsub.onboarding-test27-regsvc-sub', 'title': 'pubsub.onboarding-test27-regsvc-sub: 5 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A', 'facts': {'job': 'pubsub.onboarding-test27-regsvc-sub', 'service': 'regsvc', 'failed_runs': 5, 'error_lines': 1934, 'sample': 'failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: 401, response {\n "message": "Unauthorized: token expired"\n}\n', 'error_signature': 'failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: ?,', 'failing_at': 'pubsub/pubsub.go:151', 'trace': 'projects/tilda-trial-dev/traces/a917e57c2be767118ea8c2b8753c43ea', '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.onboarding-test27-regsvc-sub?cluster=test27&from=1794807371&to=1794828971'}, {'label': 'Background jobs', 'href': '/jobs?cluster=test27&from=1794807371&to=1794828971'}, {'label': 'Its error logs', 'href': '/logs?cluster=test27&from=1794807371&to=1794828971&severity=ERROR&q=pubsub.onboarding-test27-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-dev/traces/a917e57c2be767118ea8c2b8753c43ea?cluster=test27'}], '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': 25.0, 'status': 'resolved', 'first_seen': 1793610639, 'last_seen': 1794828971, 'resolved_at': 1794833906, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 5, 'narrative': "The background job pubsub.onboarding-test27-regsvc-sub on test27 failed 5 runs recently (1,934 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': 1223321, 'stale_s': 4989}
- 2026-11-16 17:27:13 UTCreopened x-ray · severity=warning was=warning title=pubsub.onboarding-test27-regsvc-sub: 5 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A level=medium was_level=medium finding={'id': 15295, 'fingerprint': 'ce4bded218033c85b7c2', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'test27', 'subject': 'pubsub.onboarding-test27-regsvc-sub', 'title': 'pubsub.onboarding-test27-regsvc-sub: 5 failed runs in the last 6 h — failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from A', 'facts': {'job': 'pubsub.onboarding-test27-regsvc-sub', 'service': 'regsvc', 'failed_runs': 5, 'error_lines': 2404, 'sample': 'failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: 401, response {\n "message": "Unauthorized: token expired"\n}\n', 'error_signature': 'failed to create triggers: failed to fetch existing triggers: failed to fetch triggers: Error from API call: status: ?,', 'failing_at': 'pubsublib/googlepubsub.go:697', 'trace': 'projects/tilda-trial-dev/traces/a917e57c2be76713daf38399de39a3c3', 'detected_via': 'structured error/exception field (below ERROR severity)', 'window': [1794828433, 1794850033], '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-test27-regsvc-sub?cluster=test27&from=1794828433&to=1794850033'}, {'label': 'Background jobs', 'href': '/jobs?cluster=test27&from=1794828433&to=1794850033'}, {'label': 'Its error logs', 'href': '/logs?cluster=test27&from=1794828433&to=1794850033&severity=ERROR&q=pubsub.onboarding-test27-regsvc-sub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-dev/traces/a917e57c2be76713daf38399de39a3c3?cluster=test27'}], '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': 20.0, 'status': 'open', 'first_seen': 1793610639, 'last_seen': 1794850033, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 6, 'narrative': "The background job pubsub.onboarding-test27-regsvc-sub on test27 failed 5 runs recently (1,934 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': 1794850033, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 1239428, 'stale_s': 34}
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 |