> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/portal/rule-engine/new-rule-engine/actions/advanced-settings.md).

# Advanced Settings

## Preventing Repeated Rule Notifications

When creating rules that send notifications, it is important to understand how rule retriggering works. By default, if a rule condition remains true, the action may continue to execute whenever the rule is evaluated.

For example:

```
Temperature > 30
```

If this condition remains fulfilled, the system may continue sending emails repeatedly unless retriggering settings are adjusted.

### Retriggering and Cooldown Settings

To control how often actions are executed, open your Rule Action and navigate to:

```
Advanced Settings
```

<figure><img src="/files/uxBjn2xesq5spdgOCrPX" alt=""><figcaption></figcaption></figure>

Here, you can configure how the rule behaves after the condition becomes true.

***

### Available Execution Modes

#### Execute action when conditions are becoming fulfilled

This option triggers the action only once when the condition changes from false to true.

Use this option if you only want to receive a single notification when the alarm condition first occurs.

Example:

* Temperature changes from `28°C` to `31°C`
* Condition becomes true
* One email is sent
* No further emails are sent while the condition remains true

***

#### Execute action when conditions remain fulfilled

This option allows the action to retrigger while the condition remains true.<br>

<figure><img src="/files/li4MyyZkEZje1tTVEQh8" alt=""><figcaption></figcaption></figure>

This can be useful if you want reminder notifications in case the initial alert is missed.

However, depending on the device reporting interval, this may result in frequent emails.

***

### Limiting Consecutive Executions

To avoid receiving notifications too frequently, you can enable:

```
Limit number of consecutive executions in your rule actions
```

This setting allows the rule to retrigger only a limited number of times while the condition remains fulfilled.

Example:

* Device reports every 2 minutes
* Condition remains true for 1 hour
* Rule is limited to 2 consecutive executions
* Only 2 emails are sent instead of 30

***

### Recommended Configuration

#### Send Only One Alert

Enable:

* Execute action when conditions are becoming fulfilled

Disable:

* Execute action when conditions remain fulfilled<br>

<figure><img src="/files/XImJYgkNl3vWq6a4Jr3s" alt=""><figcaption></figcaption></figure>

***

#### Send Reminder Notifications

Enable:

* Execute action when conditions remain fulfilled
* Limit number of consecutive executions in your rule actions

This configuration allows a small number of reminder notifications without flooding the recipient inbox.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datacake.de/portal/rule-engine/new-rule-engine/actions/advanced-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
