---
title: Re-notify for persistently active alert episodes in the experimental alerting system
description: How to configure action policies so a workflow re-notifies when an alert episode stays active without a status change in the experimental alerting system.
url: https://www.elastic.co/elastic/docs-builder/docs/4075/explore-analyze/alerting/experimental-alerting-system/action-policies/re-notification
products:
  - Kibana
applies_to:
  - Elastic Cloud Serverless: Experimental
  - Elastic Stack: Experimental since 9.5
---

# Re-notify for persistently active alert episodes in the experimental alerting system
Use this page to configure an action policy so a workflow keeps running while an alert episode stays active without a status change.
The `On status change` frequency option invokes a workflow once for each status transition, for example when an alert episode activates or resolves. This is efficient for reducing noise from rules in the experimental alerting system, but a persistently active alert episode that only changes in severity doesn't cause another invocation.
To re-notify for alert episodes that stay active without a status change, use a time-based throttle.
- **`At most once every…`** Invokes a workflow again after the configured interval regardless of whether severity or status changed. Setting this to `1h` invokes a workflow every hour while the alert episode remains active and matched.
- **`On status change + repeat at interval`** Invokes a workflow on status change and then repeats at the configured interval while the alert episode stays in the same status.

In this example, you want to be re-paged if a critical alert episode stays open for more than an hour. Set the action policy frequency to `At most once every 1h`. The action policy invokes a workflow when the alert episode first matches and then again each hour until the alert episode resolves or no longer matches.

| Field                | Value                     |
|----------------------|---------------------------|
| **Match conditions** | `severity: "critical"`    |
| **Notify per**       | Episode                   |
| **Frequency**        | At most once every 1 hour |
| **Destinations**     | PagerDuty workflow        |


## Related pages

- [Manage severity escalation notifications](https://www.elastic.co/elastic/docs-builder/docs/4075/explore-analyze/alerting/experimental-alerting-system/action-policies/severity-escalation): Understand how severity changes interact with action policy matching.
- [Action policy reference](https://www.elastic.co/elastic/docs-builder/docs/4075/explore-analyze/alerting/experimental-alerting-system/action-policies/action-policy-reference): Look up all frequency options.
- [Create and configure an action policy](https://www.elastic.co/elastic/docs-builder/docs/4075/explore-analyze/alerting/experimental-alerting-system/action-policies/create-configure-action-policy): Apply the frequency settings described on this page.