Repository navigation
feat(automations): Default event automation runs to 10 per minute with a configurable window - #2237
Merged
Merged
Conversation
…r hour Change the event automation run limit window from one hour to one minute. The default cap stays at 10 runs, so a single automation can now start 10 runs per rolling minute. Rename the createApp limit to maxEventAutomationRunsPerMinute (hard cutover) so the name matches the window. Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Replace maxEventAutomationRunsPerMinute with two createApp limits: maxEventAutomationRuns (default 10) and eventAutomationRunWindowMs (default 60000). Hosts that want an hourly cap can set the window to one hour. The block reason names the configured window. Co-Authored-By: David Cramer <david@sentry.io>
sentry-junior
Bot
changed the title
Move the count and window into limits.eventAutomationRunLimit
({ maxRuns, windowMs }) so hosts see they are one setting.
Co-Authored-By: David Cramer <david@sentry.io>
dcramer
approved these changes
Oct 26, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change the default event automation run limit from 10 runs per rolling hour to 10 runs per rolling minute. Hosts can also set the window now, so an hourly cap is still possible.
10 per hour blocks busy automations that are working as intended too quickly. 10 per minute still catches a runaway trigger, such as an automation that fires on every message in a busy channel.
Before this change, the one-hour window was a hardcoded constant (
EVENT_AUTOMATION_RUN_WINDOW_MS). A host could change the count but not the window.New
createApplimitBoth fields are optional, and each must be a positive integer.
Breaking:
limits.maxEventAutomationRunsPerHouris removed (hard cutover).getsentry/junior-proddoes not set it, so it needs no change.The block reason now names the configured window, for example "10 runs per minute" or "100 runs per hour". The Sentry
extrafields on the block event are nowapp.event_automation.max_runsandapp.event_automation.run_window_ms.Existing run lists in the state adapter stay compatible. Entries older than the configured window stop counting. The list TTL follows the window.
I updated the docs (
concepts/automations.md,reference/config-and-env.md) andevent-automations/README.md.Checks
pnpm --filter @sentry/junior typecheck: passes.chat-config,app-model-config, andevent-automation-blocking: all 84 tests pass.event-automations.test.tshas one failure,delivers the current automation card and retains its reference in web history. It also fails on unmodifiedmain.via David Cramer.
--
View Junior Session [Sentry]