[sentry-junior]

Part of CLI-10 ("API request failed: 400"). When sentry explore sends a user --field/--sort aggregate that Sentry rejects because of its argument, the CLI shows a raw 400 and reports it as a CLI bug. These are input mistakes: a string attribute in a numeric aggregate, transaction.duration on --dataset transactions (which queries spans), a non-numeric errors column, or an invalid count_if argument.

The CLI now reads the structured fields that getsentry/sentry#129954 (merged) adds to these 400s, "code": "invalid_function_argument" plus function and argument, instead of matching message text. ApiError keeps them next to code. When they name the same function and argument as a user expression that reached the request, toExploreFieldError (#1661) raises a ValidationError that keeps the server detail and adds a hint. Rejections of default or generated expressions, and 400s without the code (servers before that deploy), stay ApiErrors. The #1661 hints are unchanged.

Builds on #1936 for ApiError.code. Merge that first.

Before

$ sentry explore my-org/ --dataset spans -F 'p75(cart.total)'
Error: API request failed: 400 Bad Request
  Endpoint: /organizations/my-org/events/
  cart.total is invalid for parameter 1 in p75. Its a string type field, but it must be one of these types: {'number'}
# exit 30

$ sentry explore my-org/ --dataset transactions -F 'sum(transaction.duration)'
Error: API request failed: 400 Bad Request
  Endpoint: /organizations/my-org/events/
  transaction.duration is invalid for parameter 1 in sum. Its a string type field, but it must be one of these types: {'number', 'duration'}
# exit 30

After

With the server sending code, function and argument:

$ sentry explore my-org/ --dataset spans -F 'p75(cart.total)'
Error: Sentry rejected --field "p75(cart.total)" for dataset "spans".

cart.total is invalid for parameter 1 in p75. Its a string type field, but it must be one of these types: {'number'}

Try:
  p75() does not accept cart.total on dataset "spans": it may not exist there, or may not have the type p75() needs. Reference a numeric custom attribute with its type, e.g. tags[cart.total,number]; to check the key and its type, run: sentry attribute list <org>/ cart.total --dataset spans
# exit 21

$ sentry explore my-org/ --dataset transactions -F 'sum(transaction.duration)'
Error: Sentry rejected --field "sum(transaction.duration)" for dataset "spans".

transaction.duration is invalid for parameter 1 in sum. Its a string type field, but it must be one of these types: {'number', 'duration'}

Try:
  Use span.duration instead of transaction.duration. Transactions are queried as spans, which store their duration in span.duration.
# exit 21

$ sentry explore my-org/ --dataset errors -F 'min(title)'
Error: Sentry rejected --field "min(title)" for dataset "errors".

min(title): column argument invalid: title is not a numeric column

Try:
  min() does not accept title on dataset "errors": it may not exist there, or may not have the type min() needs. Check the column name and its type.
# exit 21

I captured these outputs against a local stub that returns each 400 body.

via @BYK.

--

View Session [Sentry]

[vercel]

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

Project	Deployment	Actions	Updated
sentry-local	Ready	Preview	Nov 4, 2026 9:58pm UTC

[sentry-junior]

Done. getsentry/sentry#129954 (merged) now returns "code": "invalid_function_argument" with function and argument for these 400s. This PR reads those fields and drops REJECTED_ARGUMENT_PATTERNS. A 400 without the code stays an ApiError, and there's a test for that. This builds on #1936 for ApiError.code, so merge that first.