mirror of
https://github.com/twentyhq/twenty.git
synced 2026-09-22 21:46:17 -04:00
Raphaël Bosi
0df2907b01
Follow-up to #24353, which split the workspace-setup chat's telemetry functionId but only on spans. Chat stream failures are captured as Sentry error events, and those carry no segment marker, so the ai-digest pipeline in twenty-factory cannot split error counts the way it splits spans. This sets a `chatKind` Sentry scope tag in `streamChat` with the same values as the functionId split (`ai-chat-workspace-setup-stream` / `ai-chat-stream`), so captured error events segment onboarding-vs-general exactly like spans do. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/twentyhq/twenty/pull/24387?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. -->
