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:53.
› →|
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

docproc.process: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_stat

warning Background job failing automation resolved impact 31 opened 76d ago · last observed 3d ago · observed 388× · #791 · 688d83be3e2d2c2cdce0

What happened template

The background job docproc.process on automation failed 5 runs recently (61 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

jobdocproc.process
servicedocproc
failed_runs5
error_lines61
sampleTraceback (most recent call last): File "/app/src/integrations/docsvc.py", line 34, in update_checksum_docsvc response.raise_for_status() File "/usr/local/lib/python3.12/site-packages/httpx/_models.py", line 829, in raise_for_status raise HTTPStatusError(message, request=request, respons
error_signatureTraceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_status() File ?, line ?,
failing_atutils/processing_logger.py:190
traceprojects/tilda-trial-automation/traces/98d8de56e32d935860d429448d2c83b7
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 18:48:04 UTC → 2026-11-17 00:48:04 UTC

What is failing in docproc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from docproc. In this finding's window (2026-11-16 18:48:04 UTC → 2026-11-17 00:48:04 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

2036× [786e458a-fbda-4832-86c0-f2643f4ddde6] ══════════════════════════════════════════════════════ since 2026-08-25 20:54:26 UTC
1018× [786e458a-fbda-4832-86c0-f2643f4ddde6] 0/10 slots in use since 2026-08-25 20:54:26 UTC
509× docsvc internal PATCH failed for f36d0d14-9f81-42cf-bf52-6140b0037e29: 403 {"message":"user with email not found"} since 2026-10-29 00:15:17 UTC
358× [aaf8db0d-cd5d-4719-9bb9-d0009f4c122e] Context 0.05s -> Download FAILED since 2026-08-25 20:54:27 UTC
130× [86b2d92c-e3c8-4fa0-b0b2-40c2c2da94ed] Context 0.05s -> Download 0.1s since 2026-09-12 00:17:24 UTC

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

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

History

  • 2026-11-16 11:36:11 UTCreopened x-ray · severity=warning was=warning title=docproc.process: 5 failed runs in the last 6 h — Language detection failed: no healthy upstream level=medium was_level=medium finding={'id': 791, 'fingerprint': '688d83be3e2d2c2cdce0', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'docproc.process', 'title': 'docproc.process: 5 failed runs in the last 6 h — Language detection failed: no healthy upstream', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 5, 'error_lines': 360, 'sample': 'Language detection failed: no healthy upstream', 'error_signature': 'Language detection failed: no healthy upstream', 'failing_at': 'utils/processing_logger.py:196', 'trace': 'projects/tilda-trial-automation/traces/e2e7e5789a5370100000000e759e2aef', 'detected_via': 'ERROR-severity log lines', '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/docproc.process?cluster=automation&from=1794807371&to=1794828971'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794807371&to=1794828971'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794807371&to=1794828971&severity=ERROR&q=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e5789a5370100000000e759e2aef?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': 1788520979, 'last_seen': 1794828971, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 381, 'narrative': "The background job docproc.process on automation failed 6 runs recently (105 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': 1794828971, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6308155, 'stale_s': 163}
  • 2026-11-16 15:18:05 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 791, 'fingerprint': '688d83be3e2d2c2cdce0', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'docproc.process', 'title': 'docproc.process: 6 failed runs in the last 6 h — Language detection failed: no healthy upstream', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 6, 'error_lines': 362, 'sample': 'Language detection failed: no healthy upstream', 'error_signature': 'Language detection failed: no healthy upstream', 'failing_at': 'utils/processing_logger.py:196', 'trace': 'projects/tilda-trial-automation/traces/e2e7e5789a53701fdce7b7a89b04ae98', 'detected_via': 'ERROR-severity log lines', 'window': [1794816627, 1794838227], '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/docproc.process?cluster=automation&from=1794816627&to=1794838227'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794816627&to=1794838227'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794816627&to=1794838227&severity=ERROR&q=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/e2e7e5789a53701fdce7b7a89b04ae98?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': 1788520979, 'last_seen': 1794838227, 'resolved_at': 1794842285, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 383, 'narrative': "The background job docproc.process on automation failed 6 runs recently (362 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': 1794828971, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6321336, 'stale_s': 4088}
  • 2026-11-16 20:37:48 UTCreopened x-ray · severity=warning was=warning title=docproc.process: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_stat level=medium was_level=medium finding={'id': 791, 'fingerprint': '688d83be3e2d2c2cdce0', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'docproc.process', 'title': 'docproc.process: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_stat', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 5, 'error_lines': 77, 'sample': 'Traceback (most recent call last):\n File "/app/src/integrations/docsvc.py", line 34, in update_checksum_docsvc\n response.raise_for_status()\n File "/usr/local/lib/python3.12/site-packages/httpx/_models.py", line 829, in raise_for_status\n raise HTTPStatusError(message, request=request, respons', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_status() File ?, line ?,', 'failing_at': 'utils/processing_logger.py:190', 'trace': 'projects/tilda-trial-automation/traces/a917e5733d23a349ad90171bf700a558', 'detected_via': 'ERROR-severity log lines', 'window': [1794839868, 1794861468], '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/docproc.process?cluster=automation&from=1794839868&to=1794861468'}, {'label': 'Background jobs', 'href': '/jobs?cluster=automation&from=1794839868&to=1794861468'}, {'label': 'Its error logs', 'href': '/logs?cluster=automation&from=1794839868&to=1794861468&severity=ERROR&q=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/a917e5733d23a349ad90171bf700a558?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': 1788520979, 'last_seen': 1794861468, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 384, 'narrative': "The background job docproc.process on automation failed 6 runs recently (362 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': 1794861468, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6340516, 'stale_s': 27}
  • 2026-11-17 01:53:30 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 791, 'fingerprint': '688d83be3e2d2c2cdce0', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'automation', 'subject': 'docproc.process', 'title': 'docproc.process: 5 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_stat', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 5, 'error_lines': 61, 'sample': 'Traceback (most recent call last):\n File "/app/src/integrations/docsvc.py", line 34, in update_checksum_docsvc\n response.raise_for_status()\n File "/usr/local/lib/python3.12/site-packages/httpx/_models.py", line 829, in raise_for_status\n raise HTTPStatusError(message, request=request, respons', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in update_checksum_docsvc response.raise_for_status() File ?, line ?,', 'failing_at': 'utils/processing_logger.py:190', 'trace': 'projects/tilda-trial-automation/traces/98d8de56e32d935860d429448d2c83b7', '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/docproc.process?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=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/98d8de56e32d935860d429448d2c83b7?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': 1788520979, 'last_seen': 1794876484, 'resolved_at': 1794880410, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 388, 'narrative': "The background job docproc.process on automation failed 5 runs recently (61 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': 1794861468, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 6359475, 'stale_s': 3970}

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