If an Opsgenie alert remains open after the related Sentry issue resolves, review the conditions applied to the Opsgenie action.
Conditions based only on the issue’s current priority may stop matching after the priority decreases. This can prevent de-escalation or resolution updates from being sent to Opsgenie.
Depending on the intended alert behavior, consider including The issue priority de-escalates in the Opsgenie action logic.
Use an any condition group when the action should run either when the issue reaches the configured priority or when its priority de-escalates.
Example configuration
If all conditions match:
Current issue priority is greater than or equal to medium
Send a Slack notification
If any condition matches:
Current issue priority is greater than or equal to high
The issue priority de-escalates
Send an Opsgenie notification
In this example, Slack is notified at medium or high priority, while Opsgenie is notified at high priority and can also receive later de-escalation and resolution updates.