Repository navigation
Conversation
shashjar
force-pushed
the
shashjar/feat/iswf-3705-inbox-frequency
branch
from
November 13, 2026 18:39
87e8566 to
b255042
Compare
shashjar
force-pushed
the
shashjar/feat/iswf-3705-inbox-frequency
branch
2 times, most recently
from
November 19, 2026 23:59
4a78323 to
d5fc207
Compare
Contributor
Sentry Snapshot Testing
|
shashjar
force-pushed
the
shashjar/feat/iswf-3705-inbox-frequency
branch
from
November 20, 2026 00:13
d5fc207 to
8c2ff58
Compare
shashjar
force-pushed
the
shashjar/feat/iswf-3705-inbox-frequency
branch
7 times, most recently
from
November 20, 2026 22:21
68933b3 to
73db373
Compare
Keep alert throttling per workflow/action association and record history only for eligible workflows. Refs ISWF-3705
Refs ISWF-3705
Exercise group-less eligibility with an unrestricted handler instead of setting the removed capability flag. Refs ISWF-3705
Keep the frequency and history contracts concise and remove unused fixture state. Refs ISWF-3705
shashjar
force-pushed
the
shashjar/feat/iswf-3705-inbox-frequency
branch
from
November 20, 2026 23:07
73db373 to
e48baa7
Compare
Reject unsupported actions before writing group frequency state so a later supported event can still fire. Refs ISWF-3705
Reuse the alert scenarios for Seer suppression and exclusion from group-less evaluations. Refs ISWF-3705
Require callers to provide evaluated workflow eligibility while retaining organization-scoped history filtering. Refs ISWF-3705
Contributor
decision-model-linterapi
decision-model-linter: 20 calls on 4 files, 50,105 input tokens, $0.0021, model typesafe/jev-1.13-20260917 |
Describe event validation before frequency and history, and Inbox-only eligibility without a group. Refs ISWF-3705
shashjar
marked this pull request as ready for review
November 21, 2026 17:48
This branch has not been 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.
Refs https://linear.app/getsentry/issue/ISWF-3705/support-group-less-action-invocation-and-inbox-frequency-semantics.
Inbox workflows bypass per-group frequency suppression. All non-Inbox workflows, including Seer investigation workflows, retain their existing suppression and are excluded from group-less runs. Actions must pass their handler's event validation before consuming frequency state. Eligibility is calculated per workflow/action association before equivalent actions are deduplicated for dispatch.
Immediate and delayed processing record history only for eligible workflows. This applies to existing non-Inbox workflows immediately, without a new feature flag: a workflow no longer gets a history row merely because it shares an action with an eligible workflow when its own conditions did not pass or it was frequency-suppressed.
https://app.notion.com/p/sentry/Investigation-Events-Workflow-Engine-40c8b10e4b5d80d18c4ed6c802d55d64