Skip to content

Org slug change shows generic error instead of specific “slug already in use” message #112376

@macuzi

Description

@macuzi

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Additional Notes

There was confirmation of a fix, but was able to reproduce it as of today. It looks like the backend is already sending a clear validation error for the slug, but the frontend is only showing the generic “Unable to save change” toast instead of surfacing the actual message to the user.

Steps to Reproduce

  1. Go to: Settings → Organization Settings → General.
  2. In the “Slug” field, enter a value that is already taken (for example, Sentry).
    • The change will fail, but the UI only shows a generic error.
  3. Click “Save”.

Expected Result

A clear, user‑visible validation message explaining why the change failed, e.g.:

The slug “testing” is already in use. Please choose a different slug.

Actual Result

The UI only shows a generic error toast: “Unable to save change”.

Image

To get a better description:

In the Network tab’s request list, look for the most recent request that corresponds to updating the org:

Image

Inspect the response body in the Network tab.

Image

Product Area

Settings

Link

https://testing-m4.sentry.io/settings/organization/

DSN

No response

Version

No response

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    Status

    Waiting for: Product Owner

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions