Environment
SaaS (https://sentry.io/)
Steps to Reproduce
I can always consistently reproduce it.
Reproduced in 4/4 controlled runs in one test organization.
- Configure the integration and webhook receiver before installation.
- Install it in a test organization.
- With Verify Install enabled, acknowledge installation.created,
verify via PUT /api/0/sentry-app-installations/{uuid}/ with
{"status":"installed"}, and confirm GET returns installed.
- Send distinct errors with unique fingerprints after verification.
Confirm each becomes a separate issue by resolving its event ID
through /api/0/organizations/{org}/eventids/{event_id}/.
- Record receiver traffic and the app's Dashboard Request Log.
- Continue creating distinct issues around the one-hour boundary
and after 65 minutes, without editing or reinstalling the app.
Expected Result
Issues created after the installation becomes installed produce
issue.created webhooks without an approximately one-hour blackout.
Actual Result
Early issues have no matching received webhook or Request Log entry.
Later newly created issues deliver promptly.
The most closely measured run:
- Installation observed: 2026-09-28 06:43:40 PST
- Verification: 06:45:18 PST (not logged in Sentry)
- Last issue without an observed webhook: 07:41:42 PST (+58m02s)
- First subsequent issue with a webhook: 07:43:44 PST (+60m03s)
- Further new issues also delivered.
Suspect: the organization’s cached list of installed integrations is not invalidated when an app is installed or verified, so webhook dispatch may skip it until the cache expires. The roughly 3,600-second recovery fits a fixed cache TTL, but this has not yet been confirmed as the cause of these runs.
Product Area
Settings - Developer Settings
Link
No response
DSN
No response
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
I can always consistently reproduce it.
Reproduced in 4/4 controlled runs in one test organization.
verify via PUT /api/0/sentry-app-installations/{uuid}/ with
{"status":"installed"}, and confirm GET returns installed.
Confirm each becomes a separate issue by resolving its event ID
through /api/0/organizations/{org}/eventids/{event_id}/.
and after 65 minutes, without editing or reinstalling the app.
Expected Result
Issues created after the installation becomes installed produce
issue.created webhooks without an approximately one-hour blackout.
Actual Result
Early issues have no matching received webhook or Request Log entry.
Later newly created issues deliver promptly.
The most closely measured run:
Suspect: the organization’s cached list of installed integrations is not invalidated when an app is installed or verified, so webhook dispatch may skip it until the cache expires. The roughly 3,600-second recovery fits a fixed cache TTL, but this has not yet been confirmed as the cause of these runs.
Product Area
Settings - Developer Settings
Link
No response
DSN
No response
Version
No response