sentry
sentry copied to clipboard
Published
20 hours ago •
getsentry
getsentry
Timeout check-ins do not create issues under some cases
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Create an interval cron monitor that expects a check-in every 5min
- Set the timeout time to any value longer than 5min, for example, 10min.
- Send only "in progress" check-ins every 5min
Expected Result
When the check-ins start to timeout after 10min, an issue is raised in Sentry.
Actual Result
The consecutive "in progress" check-ins seem to be preventing the timeout issue from being raised. Screenshots from two affected organisations.
Normal timeouts (with no check-in afterwards) raise issues as expected.
When check-ins are still in-progress:
Multiple timeouts:
Internal issue link Similar to this issue: https://github.com/getsentry/sentry/issues/59431
- link to test monitor: https://dev-curumas.sentry.io/issues/alerts/rules/crons/plain-python/ef57c573-124d-497e-bae7-7e2bfa057da9/details/
Product Area
Crons
Link
No response
DSN
No response
Version
No response
