Skip to content

fix: classify CONFLICT error type#5407

Merged
perkinsjr merged 1 commit intomainfrom
seer/feat/classify-conflict-error
Mar 22, 2026
Merged

fix: classify CONFLICT error type#5407
perkinsjr merged 1 commit intomainfrom
seer/feat/classify-conflict-error

Conversation

@seer-by-sentry
Copy link
Copy Markdown
Contributor

What does this PR do?

This PR addresses an issue where TRPCError with a CONFLICT code was being reported as unhandled in Sentry. The problem stemmed from the CONFLICT code being omitted from Sentry's EXPECTED_TRPC_CODES list.

To fix this:

  • 'CONFLICT' has been added to the list of recognized error codes.
  • 'warn' severity has been assigned to 'CONFLICT' errors.

This change allows for better handling and classification of duplicate resource errors, such as when a workspace slug already exists.

This fix was generated by Seer in Sentry, triggered by James Perkins. 👁️ Run ID: 12156729
Not quite right? Click here to continue debugging with Seer.

Fixes UNKEY-DASHBOARD-32

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps us understand why this PR exists

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How should this be tested?

  • Test A
  • Test B

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Ran make fmt on /go directory
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Unkey Docs if changes were necessary

@seer-by-sentry seer-by-sentry Bot requested a review from perkinsjr March 22, 2026 16:54
@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dashboard Ready Ready Preview, Comment Mar 22, 2026 4:55pm

Request Review

@perkinsjr perkinsjr changed the title feat: classify CONFLICT error type fix: classify CONFLICT error type Mar 22, 2026
@perkinsjr perkinsjr marked this pull request as ready for review March 22, 2026 16:54
@perkinsjr perkinsjr merged commit 9c62cff into main Mar 22, 2026
22 of 23 checks passed
@perkinsjr perkinsjr deleted the seer/feat/classify-conflict-error branch March 22, 2026 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant