Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 5 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-19 13:37:52.
› →|
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

execsvc: a new error shape, 44× in the last hour, never seen in 90 days (pubsub not initialized, dropping onboarding event)

warning Error never seen before master open impact 34 Owner: Madhava Mukkamala (backup: Shashank Agrawal) opened 2d ago · last observed 2d ago · observed 3× · #17372 · 4a9da3893ffdecb1f46c

What happened template

execsvc logged “pubsub not initialized, dropping onboarding event” 44 times in the last hour and never before in 90 days on master (first seen 2026-11-16 07:26 UTC, raised at health/util.go:145). Example trace: df85a2172dcd3a30d3260b366d781790.

An error shape appearing for the first time in 90 days, five or more times in an hour.

The facts

serviceexecsvc
callerhealth/util.go:145
shapepubsub not initialized, dropping onboarding event
count44
error_class—
first_seen2026-11-16 07:26:10 UTC (2d ago)
samplepubsub not initialized, dropping onboarding event
tracedf85a2172dcd3a30d3260b366d781790
shape_hash5cad003440a740d7
count_is_floorno
discriminator5cad003440a740d7
window2026-11-16 07:15:41 UTC → 2026-11-16 08:15:41 UTC

What is failing in execsvc — the bad events, decomposed

“Bad events” are HTTP 5xx answers from execsvc. In this finding's window (2026-11-16 07:15:41 UTC → 2026-11-16 08:15:41 UTC) there were 0; every line links to the grouped errors behind it.

The error shapes behind them

787× Request completed — 500 · failed to fetch activity status: could not match participant question to activity graph: quest… since 2026-10-16 12:11:42 UTC
787× Failed to fetch activity status — could not match participant question to activity graph: questionId="b3228925-d16e-41cf… since 2026-11-04 11:18:42 UTC
787× could not match participant questionnaire/question/table/doc-upload to activity graph since 2026-11-17 04:05:17 UTC
44× pubsub not initialized, dropping onboarding event since 2026-11-16 07:26:10 UTC
30× No cached node found for activation chain ref node since 2026-11-12 13:43:21 UTC

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

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

  • 2026-11-16 07:00:00 UTClatency execsvc p95 peaked at 2.81 s
  • 2026-11-16 07:34:54 UTCthis finding execsvc: a new error shape, 44× in the last hour, never seen in 90 days (pubsub not initialized, dropping onboarding event)
  • 2026-11-16 08:05:51 UTCdeploy automated deployed execsvc

History

  • 2026-11-16 07:34:54 UTCopened x-ray · severity=warning title=execsvc: a new error shape, 44× in the last hour, never seen in 90 days (pubsub not initialized, dropping onboarding event) finding={'id': 17372, 'fingerprint': '4a9da3893ffdecb1f46c', 'kind': 'error.novel', 'severity': 'warning', 'cluster': 'master', 'subject': 'execsvc', 'title': 'execsvc: a new error shape, 44× in the last hour, never seen in 90 days (pubsub not initialized, dropping onboarding event)', 'facts': {'service': 'execsvc', 'caller': 'health/util.go:145', 'shape': 'pubsub not initialized, dropping onboarding event', 'count': 44, 'error_class': None, 'first_seen': 1794813970, 'sample': 'pubsub not initialized, dropping onboarding event', 'trace': 'df85a2172dcd3a30d3260b366d781790', 'shape_hash': '5cad003440a740d7', 'window': [1794810894, 1794814494], 'count_is_floor': False, 'discriminator': '5cad003440a740d7'}, 'evidence': [{'label': 'Errors, grouped', 'href': '/errors?cluster=master&from=1794810894&to=1794814494&service=execsvc'}, {'label': 'Logs', 'href': '/logs?cluster=master&from=1794810894&to=1794814494&service=execsvc&severity=ERROR'}, {'label': 'Example trace', 'href': '/trace/df85a2172dcd3a30d3260b366d781790?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': 'Cloud Logging, last hour, grouped by (service, caller, shape)'}, 'impact': 32.8, 'status': 'open', 'first_seen': 1794814494, 'last_seen': 1794814494, 'resolved_at': None, 'acked_by': None, 'acked_at': None, 'snoozed_until': None, 'occurrences': 1, 'narrative': None, 'narrative_kind': None, 'discriminator': '5cad003440a740d7', 'level': 'medium', 'told_level': None, 'episode_at': 1794814494, 'chat_thread': None, 'kind_label': 'Error never seen before', 'group': 'Errors', 'age_s': 35, 'stale_s': 35}

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
noteCloud Logging, last hour, grouped by (service, caller, shape)
detectorerrors_novel