Skip to content

fix(Tracing): Check for AI operation id to detect a vercelai span #18824

Closed

Description

@github-actions

Note

The pull request "fix(Tracing): Check for AI operation id to detect a vercelai span" was created by @RulaKhaled but did not reference an issue. Therefore this issue was created for better visibility in external tools like Linear.

Resolves an issue where spans weren’t being processed because v6 emits spans with a "default" name. We now validate using both the span name (v5) and the operation ID (v6).

Activity

  1. linear commented on Jan 15, 2026

    @linear
  2. added a commit that references this issue on Jan 15, 2026
    7640856
  3. github-actions commented on Jan 19, 2026

    @github-actions
    ContributorAuthor

    A PR closing this issue has just been released 🚀

    This issue was referenced by PR #18823, which was included in the 10.35.0 release.

  4. rodolfoBee commented on Jan 23, 2026

    @rodolfoBee
    Member

    Reopening this issue as one affected user is reporting the issue continues after updating to v10.35.0.

  5. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Jan 23, 2026
  6. JPeer264 commented on Jan 23, 2026

    @JPeer264
    Member

    @RulaKhaled could you take a look?

  7. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Jan 23, 2026
  8. 24 remaining items

  9. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Feb 3, 2026
  10. RulaKhaled commented on Feb 3, 2026

    @RulaKhaled
    Collaborator

    Are you using Next.js 16+? There’s a known issue where the AI SDK isn’t going through the Sentry processor. This is still under investigation, and we’ll update this issue as we learn more.

  11. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Feb 3, 2026
  12. AlonSh commented on Feb 4, 2026

    @AlonSh

    Yes we are! Is there an issue I can subscribe to?

  13. moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Feb 4, 2026
  14. RulaKhaled commented on Feb 4, 2026

    @RulaKhaled
    Collaborator
  15. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Feb 4, 2026
  16. RulaKhaled commented on Feb 4, 2026

    @RulaKhaled
    Collaborator

    :announcement: I will be closing this ticket in favor of JS-1627. For everyone affected, if you are experiencing the same issue, please follow updates on the new ticket.

    gh issue: https://github.com/getsentry/sentry-javascript/issues/19147

  17. AlonSh commented on Feb 4, 2026

    @AlonSh

    Thanks!
    We don't have access to your linear project though, is there a matching github issue?

  18. RulaKhaled commented on Feb 4, 2026

    @RulaKhaled
    Collaborator

    Oh for sure, can you view #19147?

    Also a quick update, setting force: true in vercelAIIntegration should resolve this issue

    integrations: [
       Sentry.vercelAIIntegration({force: true }),
    ],
    
  19. AlonSh commented on Feb 4, 2026

    @AlonSh

    That works!
    I'll also follow that ticket for better resolution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions