Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 30 days▾
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 02:12:33.
› →|
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.study-site-binding-test27-regsub: 5 failed runs in the last 6 h — internal code issue: Trying to commit a transaction which never started

warning Background job failing test27 resolved impact 25 opened 58d ago · last observed 3d ago · observed 200× · #2013 · f31a29e4c393a047d3d1

What happened template

The background job pubsub.study-site-binding-test27-regsub on test27 failed 5 runs recently (15 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.study-site-binding-test27-regsub
serviceregsvc
failed_runs5
error_lines15
sampleinternal code issue: Trying to commit a transaction which never started
error_signatureinternal code issue: Trying to commit a transaction which never started
failing_atpubsub/pubsub.go:692
traceprojects/tilda-trial-dev/traces/3d974b8c29b78180b21e806431e89954
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-15 10:31:04 UTC → 2026-11-15 16:31:04 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-15 10:31:04 UTC → 2026-11-15 16:31:04 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
82× workflow is already published for site since 2026-11-03 23:53:36 UTC
42× message was never published because transaction was never committed since 2026-11-03 23:54:59 UTC
42× failed to commit transaction — internal code issue: Trying to commit a transaction which never started since 2026-11-03 23:53:22 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-15 17:35:45 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 2013, 'fingerprint': 'f31a29e4c393a047d3d1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'test27', 'subject': 'pubsub.study-site-binding-test27-regsub', 'title': 'pubsub.study-site-binding-test27-regsub: 5 failed runs in the last 6 h — internal code issue: Trying to commit a transaction which never started', 'facts': {'job': 'pubsub.study-site-binding-test27-regsub', 'service': 'regsvc', 'failed_runs': 5, 'error_lines': 15, 'sample': 'internal code issue: Trying to commit a transaction which never started', 'error_signature': 'internal code issue: Trying to commit a transaction which never started', 'failing_at': 'pubsub/pubsub.go:692', 'trace': 'projects/tilda-trial-dev/traces/3d974b8c29b78180b21e806431e89954', 'detected_via': 'ERROR-severity log lines', 'window': [1794738664, 1794760264], '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.study-site-binding-test27-regsub?cluster=test27&from=1794738664&to=1794760264'}, {'label': 'Background jobs', 'href': '/jobs?cluster=test27&from=1794738664&to=1794760264'}, {'label': 'Its error logs', 'href': '/logs?cluster=test27&from=1794738664&to=1794760264&severity=ERROR&q=pubsub.study-site-binding-test27-regsub'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-dev/traces/3d974b8c29b78180b21e806431e89954?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': 1789998264, 'last_seen': 1794760264, 'resolved_at': 1794764145, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 200, 'narrative': "The background job pubsub.study-site-binding-test27-regsub on test27 failed 5 runs recently (15 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': 1794602317, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 4765926, 'stale_s': 3926}

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