[sentry-junior]

sentry explore <org>/<project> scoped the Events request with a project:<slug> query term and sent no project param. The API checks that term against the requester's member projects only. So if you query a valid project you aren't a member of, the request 400s. This is one of the root causes grouped under CLI-10 ("API request failed: 400"), hitting several orgs on 0.47.0.

The fix copies trace/span/log list (#1317). Explore now resolves the numeric project ID with resolveLogProjectId and sends project=<id> for table queries, --time-series, and --metric discovery. It still falls back to project:<slug> when the ID can't be resolved. Replays already scope with projectSlugs and are unchanged. A slug that doesn't exist now gets the existing "Project not found" resolution error with suggestions, not a raw 400.

Before

$ sentry explore my-org/my-proj -F title -F "count()"
Error: API request failed: 400 Bad Request
  Endpoint: /organizations/my-org/events/
  Invalid query. Project(s) my-proj do not exist or are not actively selected.

GET /api/0/organizations/my-org/events/?dataset=errors&field=title&field=count()&query=project:my-proj&sort=-count()&per_page=25&statsPeriod=24h

After

$ sentry explore my-org/my-proj -F title -F "count()"
Querying errors in my-org/my-proj:

╭────────────────────────────────────────────────┬─────────╮
│ TITLE                                          │ COUNT() │
├────────────────────────────────────────────────┼─────────┤
│ TypeError: Cannot read properties of undefined │     128 │
│ ReferenceError: foo is not defined             │      12 │
╰────────────────────────────────────────────────┴─────────╯

Showing 2 results.

GET /api/0/projects/my-org/my-proj/?collapse=organization
GET /api/0/organizations/my-org/events/?dataset=errors&field=title&field=count()&project=42&sort=-count()&per_page=25&statsPeriod=24h

The output above came from a local fake Sentry server that rejects project:<slug> without a project param, which matches the production error.

via bete.

--

View Session [Sentry]

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Nov 4, 2026 9:49am UTC

[BYK]

Because why not? 🤣