Creating an org auth token through UI hangs, creates duplicates
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Creating an organization auth token (Settings → Auth Tokens → Create New Token) can hang indefinitely in the UI, eventually resolve to a 504, and silently create multiple duplicate tokens server-side that are never surfaced to the user.
- Go to Settings > Auth Tokens > New Token in an organization.
- Enter a name, click Create Token.
- Observe the button/loading state.
Could not reproduce in my org, could reliably reproduce in the customer's org. Please see the internal Linear ticket for details.
Expected Result
Request completes quickly and the new token secret is displayed
Actual Result
Infinite spinner, no token shown, but multiple tokens get created behind the scenes.
Product Area
Settings - Developer Settings
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Settings → Auth Tokens → Create New Token flow in the SaaS environment and review the internal Linear ticket for the customer-specific details. Trace the request from submission through token creation; done means the request completes promptly, exactly one token is created, and its secret is displayed instead of an indefinite spinner or 504.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100