docproc.process: 8 failed runs in the last 6 h — No docsvc authorization (caller token or TildaSense bot token)
warning
Background job failing
master
resolved
impact 38
opened 2d ago · last observed 2d ago · observed 7× · #17338 · 3148a2d3192815bcb29d
What happened template
The background job docproc.process on master failed 8 runs recently (71 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 | docproc.process |
| service | docproc |
| failed_runs | 8 |
| error_lines | 71 |
| sample | No docsvc authorization (caller token or TildaSense bot token) |
| error_signature | No docsvc authorization (caller token or TildaSense bot token) |
| failing_at | utils/processing_logger.py:190 |
| trace | projects/tilda-trial-automation/traces/01b63551a1d4a3740a34c6234f6c8664 |
| 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-15 23:18:52 UTC → 2026-11-16 05:18:52 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-15 23:18:52 UTC → 2026-11-16 05:18:52 UTC) there were 0; every line links to the grouped errors behind it.
The error shapes behind them
| 38× | Failed to create document processing AIRun — aborting pipeline (refuse to run untracked) — No docsvc authorization (call… since 2026-11-15 21:16:35 UTC |
| 38× | docsvc PATCH aiEnabled failed before creating AI run since 2026-11-15 21:16:35 UTC |
| 29× | ServiceTokenManager refresh failed (429 Client Error: Too Many Requests for url: https://login.tilda.pizza/oauth/token) … since 2026-11-15 21:16:35 UTC |
| 23× | [90814349-b97c-4cf0-b423-9decc2a42448] PubSub certify failed: AIRun creation failed for document 90814349-b97c-4cf0-b423… since 2026-11-01 21:47:55 UTC |
| 10× | Recovery failed — AIRun creation failed for document 708e1425-a271-4065-9830-6f906d9e1004 (document processing): No docs… since 2026-11-15 21:17:08 UTC |
The story — No docproc deploy or hand change is recorded in the hour before this opened. Everything below is docproc only.
- 2026-11-15 22:03:48 UTCfinding · warning docproc: a new error shape, 5× in the last hour, never seen in 90 days (docsvc call not possible)
- 2026-11-15 22:39:56 UTCfinding · warning docproc: a new error shape, 5× in the last hour, never seen in 90 days ([?] Pubsub:Attribute Update failed: AIRun creation failed for document)
- 2026-11-15 23:02:23 UTCthis finding docproc.process: 8 failed runs in the last 6 h — No docsvc authorization (caller token or TildaSense bot token)
- 2026-11-16 00:50:21 UTCfinding · warning docproc: a new error shape, 5× in the last hour, never seen in 90 days ([?] PIPELINE FAILED — 101_1572_Ruiz_02Nov2026.pdf — RuntimeError: docs)
- 2026-11-16 00:50:21 UTCfinding · warning docproc: a new error shape, 5× in the last hour, never seen in 90 days ([?] PIPELINE FAILED — 101_1572_Ruiz_02Nov2026.pdf — Error: docsvc chec)
- 2026-11-16 00:50:21 UTCfinding · warning docproc: a new error shape, 5× in the last hour, never seen in 90 days (docsvc checksum update skipped: no agent token (configure TildaSense b)
- 2026-11-16 01:19:23 UTCdeploy automated deployed docproc
- 2026-11-16 05:00:00 UTClatency docproc p95 peaked at 2.67 s
- 2026-11-16 05:19:59 UTCdeploy automated deployed docproc
History
- 2026-11-15 23:02:23 UTCopened x-ray · severity=warning title=docproc.process: 9 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in _refresh self._do_password_grant() File ?, lin finding={'id': 17338, 'fingerprint': '3148a2d3192815bcb29d', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'master', 'subject': 'docproc.process', 'title': 'docproc.process: 9 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in _refresh self._do_password_grant() File ?, lin', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 9, 'error_lines': 45, 'sample': 'Traceback (most recent call last):\n File "/usr/local/lib/python3.12/site-packages/tilda_auth/service_token_manager.py", line 169, in _refresh\n self._do_password_grant()\n File "/usr/local/lib/python3.12/site-packages/tilda_auth/service_token_manager.py", line 224, in _do_password_grant\n respo', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in _refresh self._do_password_grant() File ?, line ?, in _do_password', 'failing_at': 'utils/processing_logger.py:190', 'trace': 'projects/tilda-trial-automation/traces/9cded473aed184d50d489b938ac5b8e4', 'detected_via': 'ERROR-severity log lines', 'window': [1794762143, 1794783743], '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=master&from=1794762143&to=1794783743'}, {'label': 'Background jobs', 'href': '/jobs?cluster=master&from=1794762143&to=1794783743'}, {'label': 'Its error logs', 'href': '/logs?cluster=master&from=1794762143&to=1794783743&severity=ERROR&q=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/9cded473aed184d50d489b938ac5b8e4?cluster=master'}], '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': 33.4, 'status': 'open', 'first_seen': 1794783743, 'last_seen': 1794783743, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1, 'narrative': None, 'narrative_kind': None, 'discriminator': '', 'level': 'medium', 'told_level': None, 'episode_at': 1794783743, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 48, 'stale_s': 48}
- 2026-11-16 01:09:28 UTCescalated x-ray · severity=warning was=warning title=docproc.process: 23 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in _refresh self._do_password_grant() File ?, lin level=high was_level=medium finding={'id': 17338, 'fingerprint': '3148a2d3192815bcb29d', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'master', 'subject': 'docproc.process', 'title': 'docproc.process: 23 failed runs in the last 6 h — Traceback (most recent call last): File ?, line ?, in _refresh self._do_password_grant() File ?, lin', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 23, 'error_lines': 156, 'sample': 'Traceback (most recent call last):\n File "/usr/local/lib/python3.12/site-packages/tilda_auth/service_token_manager.py", line 169, in _refresh\n self._do_password_grant()\n File "/usr/local/lib/python3.12/site-packages/tilda_auth/service_token_manager.py", line 224, in _do_password_grant\n respo', 'error_signature': 'Traceback (most recent call last): File ?, line ?, in _refresh self._do_password_grant() File ?, line ?, in _do_password', 'failing_at': 'utils/processing_logger.py:190', 'trace': 'projects/tilda-trial-automation/traces/01b63551a1d4a3740a34c6234f6c8664', 'detected_via': 'ERROR-severity log lines', 'window': [1794769768, 1794791368], '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=master&from=1794769768&to=1794791368'}, {'label': 'Background jobs', 'href': '/jobs?cluster=master&from=1794769768&to=1794791368'}, {'label': 'Its error logs', 'href': '/logs?cluster=master&from=1794769768&to=1794791368&severity=ERROR&q=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/01b63551a1d4a3740a34c6234f6c8664?cluster=master'}], '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': 33.2, 'status': 'open', 'first_seen': 1794783743, 'last_seen': 1794791368, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 3, 'narrative': "The background job docproc.process on master failed 15 runs recently (85 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': 'high', 'told_level': None, 'episode_at': 1794783743, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 7677, 'stale_s': 52}
- 2026-11-16 06:22:27 UTCresolved x-ray · reason=not observed grace_s=900 finding={'id': 17338, 'fingerprint': '3148a2d3192815bcb29d', 'kind': 'job.failing', 'severity': 'warning', 'cluster': 'master', 'subject': 'docproc.process', 'title': 'docproc.process: 8 failed runs in the last 6 h — No docsvc authorization (caller token or TildaSense bot token)', 'facts': {'job': 'docproc.process', 'service': 'docproc', 'failed_runs': 8, 'error_lines': 71, 'sample': 'No docsvc authorization (caller token or TildaSense bot token)', 'error_signature': 'No docsvc authorization (caller token or TildaSense bot token)', 'failing_at': 'utils/processing_logger.py:190', 'trace': 'projects/tilda-trial-automation/traces/01b63551a1d4a3740a34c6234f6c8664', 'detected_via': 'ERROR-severity log lines', 'window': [1794784732, 1794806332], '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=master&from=1794784732&to=1794806332'}, {'label': 'Background jobs', 'href': '/jobs?cluster=master&from=1794784732&to=1794806332'}, {'label': 'Its error logs', 'href': '/logs?cluster=master&from=1794784732&to=1794806332&severity=ERROR&q=docproc.process'}, {'label': 'Example trace', 'href': '/trace/projects/tilda-trial-automation/traces/01b63551a1d4a3740a34c6234f6c8664?cluster=master'}], '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': 37.9, 'status': 'resolved', 'first_seen': 1794783743, 'last_seen': 1794806332, 'resolved_at': 1794810147, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 7, 'narrative': "The background job docproc.process on master failed 8 runs recently (71 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': 1794783743, 'chat_thread': None, 'kind_label': 'Background job failing', 'group': 'Jobs', 'age_s': 26464, 'stale_s': 3875}
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 |