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-21 04:09:50.
› →|
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

exportsvc.activity_update: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s

warning Background job failing automation resolved impact 31 opened 76d ago · last observed 3d ago · observed 484× · #868 · b28f7e4a035d1377f5f1

What happened template

The background job exportsvc.activity_update on automation failed 5 runs recently (129 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

jobexportsvc.activity_update
serviceexportsvc
failed_runs5
error_lines129
sampleTraceback (most recent call last): File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle await handle_activity_update(message, self.config, self.gcs_client) File "/app/src/app/worker/handlers/activity_update_handler.py", line 336, in handle_activity_updat
error_signatureTraceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs
failing_athandlers/activity_update_handler_wrapper.py:86
traceprojects/tilda-trial-automation/traces/e2e7e573b27ea45b7fb1b3f688061688
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 20:54:44 UTC → 2026-11-17 02:54:44 UTC

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

History

  • 2026-11-15 00:25:54 UTCreopened x-ray · severity=warning was=warning title=exportsvc.activity_update: 6 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s level=medium was_level=medium finding={'id': 868, 'fingerprint': 'b28f7e4a035d1377f5f1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'exportsvc.activity_update', 'title': 'exportsvc.activity_update: 6 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s', 'facts': {'job': 'exportsvc.activity_update', 'service': 'exportsvc', 'failed_runs': 6, 'error_lines': 90, 'sample': 'Traceback (most recent call last):\n File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle\n await handle_activity_update(message, self.config, self.gcs_client)\n File "/app/src/app/worker/handlers/activity_update_handler.py", line 336, in handle_activity_updat', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs', 'failing_at': 'handlers/activity_update_handler_wrapper.py:86', 'trace': 'projects/tilda-trial-automation/traces/e2e7e57f77b69157cc8f66b13b6e8362', '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/exportsvc.activity_update?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=exportsvc.activity_update'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e57f77b69157cc8f66b13b6e8362?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': 1788563014, 'last_seen': 1794702354, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 467, 'narrative': "The background job exportsvc.activity_update on automation failed 7 runs recently (128 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': 1794702354, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6139383, 'stale_s': 43}
  • 2026-11-15 04:49:55 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 868, 'fingerprint': 'b28f7e4a035d1377f5f1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'exportsvc.activity_update', 'title': 'exportsvc.activity_update: 6 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s', 'facts': {'job': 'exportsvc.activity_update', 'service': 'exportsvc', 'failed_runs': 6, 'error_lines': 90, 'sample': 'Traceback (most recent call last):\n File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle\n await handle_activity_update(message, self.config, self.gcs_client)\n File "/app/src/app/worker/handlers/activity_update_handler.py", line 336, in handle_activity_updat', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs', 'failing_at': 'handlers/activity_update_handler_wrapper.py:86', 'trace': 'projects/tilda-trial-automation/traces/e2e7e57f77b69157cc8f66b13b6e8362', 'detected_via': 'ERROR-severity log lines', 'window': [1794692647, 1794714247], '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/exportsvc.activity_update?cluster=automation&from=1794692647&to=1794714247'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794692647&to=1794714247'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794692647&to=1794714247&severity=ERROR&q=exportsvc.activity_update'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e57f77b69157cc8f66b13b6e8362?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': 1788563014, 'last_seen': 1794714247, 'resolved_at': 1794718195, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 470, 'narrative': "The background job exportsvc.activity_update on automation failed 6 runs recently (90 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': 1794702354, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6155229, 'stale_s': 3996}
  • 2026-11-16 00:04:59 UTCreopened x-ray · severity=warning was=warning title=exportsvc.activity_update: 9 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s level=medium was_level=medium finding={'id': 868, 'fingerprint': 'b28f7e4a035d1377f5f1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'exportsvc.activity_update', 'title': 'exportsvc.activity_update: 9 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s', 'facts': {'job': 'exportsvc.activity_update', 'service': 'exportsvc', 'failed_runs': 9, 'error_lines': 149, 'sample': 'Traceback (most recent call last):\n File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle\n await handle_activity_update(message, self.config, self.gcs_client)\n File "/app/src/app/worker/handlers/activity_update_handler.py", line 235, in handle_activity_updat', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs', 'failing_at': 'handlers/activity_update_handler_wrapper.py:86', 'trace': 'projects/tilda-trial-automation/traces/e2e7e575c568620957f7ce95186bf563', 'detected_via': 'ERROR-severity log lines', 'window': [1794765899, 1794787499], '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/exportsvc.activity_update?cluster=automation&from=1794765899&to=1794787499'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794765899&to=1794787499'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794765899&to=1794787499&severity=ERROR&q=exportsvc.activity_update'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e575c568620957f7ce95186bf563?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': 1788563014, 'last_seen': 1794787499, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 471, 'narrative': "The background job exportsvc.activity_update on automation failed 6 runs recently (90 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': 1794787499, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6224527, 'stale_s': 42}
  • 2026-11-16 20:37:48 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 868, 'fingerprint': 'b28f7e4a035d1377f5f1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'exportsvc.activity_update', 'title': 'exportsvc.activity_update: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s', 'facts': {'job': 'exportsvc.activity_update', 'service': 'exportsvc', 'failed_runs': 5, 'error_lines': 70, 'sample': 'Traceback (most recent call last):\n File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle\n await handle_activity_update(message, self.config, self.gcs_client)\n File "/app/src/app/worker/handlers/activity_update_handler.py", line 336, in handle_activity_updat', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs', 'failing_at': 'handlers/activity_update_handler_wrapper.py:86', 'trace': 'projects/tilda-trial-automation/traces/e2e7e57c176f9e890c333ee748d23016', 'detected_via': 'ERROR-severity log lines', 'window': [1794801012, 1794822612], '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/exportsvc.activity_update?cluster=automation&from=1794801012&to=1794822612'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794801012&to=1794822612'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794801012&to=1794822612&severity=ERROR&q=exportsvc.activity_update'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e57c176f9e890c333ee748d23016?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': 1788563014, 'last_seen': 1794822612, 'resolved_at': 1794861468, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 480, 'narrative': "The background job exportsvc.activity_update on automation failed 5 runs recently (70 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': 1794787499, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6298482, 'stale_s': 38884}
  • 2026-11-16 23:44:07 UTCreopened x-ray · severity=warning was=warning title=exportsvc.activity_update: 6 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s level=medium was_level=medium finding={'id': 868, 'fingerprint': 'b28f7e4a035d1377f5f1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'exportsvc.activity_update', 'title': 'exportsvc.activity_update: 6 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s', 'facts': {'job': 'exportsvc.activity_update', 'service': 'exportsvc', 'failed_runs': 6, 'error_lines': 132, 'sample': 'Traceback (most recent call last):\n File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle\n await handle_activity_update(message, self.config, self.gcs_client)\n File "/app/src/app/worker/handlers/activity_update_handler.py", line 336, in handle_activity_updat', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs', 'failing_at': 'handlers/activity_update_handler_wrapper.py:86', 'trace': 'projects/tilda-trial-automation/traces/e2e7e573b27ea45b7fb1b3f688061688', '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/exportsvc.activity_update?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=exportsvc.activity_update'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e573b27ea45b7fb1b3f688061688?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': 1788563014, 'last_seen': 1794872647, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 481, 'narrative': "The background job exportsvc.activity_update on automation failed 5 runs recently (70 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': 1794872647, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6309663, 'stale_s': 30}
  • 2026-11-17 04:00:15 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 868, 'fingerprint': 'b28f7e4a035d1377f5f1', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'exportsvc.activity_update', 'title': 'exportsvc.activity_update: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, s', 'facts': {'job': 'exportsvc.activity_update', 'service': 'exportsvc', 'failed_runs': 5, 'error_lines': 129, 'sample': 'Traceback (most recent call last):\n File "/app/src/app/worker/handlers/activity_update_handler_wrapper.py", line 67, in handle\n await handle_activity_update(message, self.config, self.gcs_client)\n File "/app/src/app/worker/handlers/activity_update_handler.py", line 336, in handle_activity_updat', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in handle await handle_activity_update(message, self.config, self.gcs', 'failing_at': 'handlers/activity_update_handler_wrapper.py:86', 'trace': 'projects/tilda-trial-automation/traces/e2e7e573b27ea45b7fb1b3f688061688', 'detected_via': 'ERROR-severity log lines', 'window': [1794862484, 1794884084], '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/exportsvc.activity_update?cluster=automation&from=1794862484&to=1794884084'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794862484&to=1794884084'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794862484&to=1794884084&severity=ERROR&q=exportsvc.activity_update'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e573b27ea45b7fb1b3f688061688?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': 1788563014, 'last_seen': 1794884084, 'resolved_at': 1794888015, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 484, 'narrative': "The background job exportsvc.activity_update on automation failed 5 runs recently (129 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': 1794872647, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6325045, 'stale_s': 3975}

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