0
Time outs do not create issues
Source: getsentry/sentry#59431 · opened by @InterstellarStella
Environment SaaS ( Steps to Reproduce For testing purposes: 1. Set up a cron monitor for a 3 minute interval, 5 minute grace period and 7 minute max runtime, and set it to notify your email 2. Use postman and [this endpoint]( to create an in_progress checkin ![image]( 3. Wait until the In Progress status turns to Timed Out [in the Sentry Web UI]( Expected Result After 7 minutes the checkin should be marked as Timed Out, create an issue, and notify your email. Actual Result No issue is created due to the time out, and no email notification is sent. This has caused a customer to miss a multi-hour failure. I also tested the same thing with missed and failed checkins, both of which seem to be creating new issues and sending an email. If we mark those issues as resolved, and test the same situations again, the issues will be marked as regressed, so this part works fine. Links from my test org: • [monitor]( • [missed checkin issue]( • [failed checkin issue]( Lin…
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow setting properties of user outside of events
0 votes · 0 comments
Extend similar-issue detection across projects, not only within a single project
0 votes · 0 comments
Ability to multi-select issues and assign an owner from the feed
0 votes · 0 comments
Cron issues not triggering issue webhooks
0 votes · 0 comments
Sort issues feed by ingestion date
0 votes · 0 comments
No comments yet.