Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting error "The organization you were looking for was not found." when trying to access session replays #53431

Closed
xliee opened this issue Jul 24, 2023 · 7 comments · Fixed by #53451

Comments

@xliee
Copy link

xliee commented Jul 24, 2023

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

When you access the replays list (in https://example.com/organizations/{organization_slug}/replays)
and click one of the replays, it redirects you to, https://example.com/replays/1461d5f133fa4e8d8914b607b314efcb/...
there appears this error
image

The correct url should indeed be https://example.com/organizations/sentry/replays/1461d5f133fa4e8d8914b607b314efcb/...
image

The organizations/${organization.slug}/ is missing (https://github.com/getsentry/sentry/pull/52933/files#diff-deb3934bfd12ee1ede62177d72424cfe226a9a3a15d97feb36588b9e3f8ebbba)

The bug was introduced as a solution to #51541 in #52933 PR.
This issue is a duplicate from getsentry/self-hosted#2291

Expected Result

https://example.com/replays/1461d5f133fa4e8d8914b607b314efcb/

Actual Result

https://example.com/organizations/sentry/replays/1461d5f133fa4e8d8914b607b314efcb/

Product Area

Replays

Link

No response

DSN

No response

Version

Sentry 23.8.0.dev0 97c76f2

@getsantry
Copy link
Contributor

getsantry bot commented Jul 24, 2023

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Jul 24, 2023

Routing to @getsentry/product-owners-replays for triage ⏲️

@JoshFerge
Copy link
Member

noticed internally as well: https://github.com/getsentry/team-replay/issues/116. will prioritize a fix here!

@ryan953 ryan953 self-assigned this Jul 24, 2023
@ryan953 ryan953 linked a pull request Jul 24, 2023 that will close this issue
@bruno-garcia
Copy link
Member

@xliee A fix was merged:

Could you please update to the latest commit and let us know it solved the problem?

@alkanna
Copy link

alkanna commented Jul 24, 2023

@bruno-garcia Updated to latest commit and can confirm it's working great now, thanks !

@xliee
Copy link
Author

xliee commented Jul 25, 2023

@xliee A fix was merged:

Could you please update to the latest commit and let us know it solved the problem?

Yes it is fixed. Thanks!

@bruno-garcia
Copy link
Member

Thanks!

@github-actions github-actions bot locked and limited conversation to collaborators Aug 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants