Skip to content

fix(alerts): Make ProjectRuleStatsIndexEndpoint 400 on a bad date range

b4b74c6
Select commit
Loading
Failed to load commit list.
Merged

fix(alerts): Make ProjectRuleStatsIndexEndpoint 400 on a bad date range #112505

fix(alerts): Make ProjectRuleStatsIndexEndpoint 400 on a bad date range
b4b74c6
Select commit
Loading
Failed to load commit list.
getsantry / getsentry / backend completed Apr 8, 2026 in 3m 49s

Mixed (backend: skipped, migration-tests: success)

View the workflow run on getsentry

Running against master

Details

More information

What is this?

This is a check to make sure your Pull Request passes tests on our private getsentry repo. We use GitHub Actions to
dispatch a workflow run on getsentry which creates this Check and eventually reports back the test results.

Read the below point on what to do if this Pull Request requires changes in getsentry.

What do I do if this is failing?

First, make sure your branch on sentry is update to date with master,
as getsentry could be depending on a change that exists in master but
does not yet exist on your feature branch.

If this check is still failing, it probably means the test(s) on getsentry are broken.

You will need to open a PR on getsentry, fix the problem, and add

Requires https://github.com/getsentry/sentry/pull/112505

in the PR description (NOT a comment) to have it run against this PR.