FeatureFuel
0

Cron issues not triggering issue webhooks

Source: getsentry/sentry#98048 · opened by @rodolfoBee
Environment

SaaS (

Steps to Reproduce

1. Create an internal integration
2. Add a webhook endpoint
3. Enable "Issue" webhook for "created, resolved, assigned, archived, unresolved"
4. Create a cron monitor alert
5. Trigger a failure in the cron monitor

Expected Result

Sentry sends a "Issue created" webhook request to the defined in the internal integration.

The webhook documentation does not mention limitations on which kind of issues can trigger webhooks, thus it is expected that all issues can trigger webhooks.

Actual Result

No webhook is sent.

Scenarios where no webhook request is sent:
1. Cron monitor issue creation
2. Cron monitor issue auto-resolve by new OK check-in


Scenarios where a webhook request is sent:
1. Cron monitor issue automatically assigned
2. Cron monitor issue manually resolved

Product Area

Settings - Integrations

Link

_No response_

DSN

_No response_

Version

_No response_

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests