> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/knowledge-base/alerting-and-notifications/why-are-my-ilert-calls-being-discarded-due-to-a-temporary-limit.md).

# Why are my ilert calls being discarded due to a temporary limit?

This article explains why you might see notifications indicating ilert calls were "discarded due to a temporary limit," causing unintended escalations, and provides steps to resolve this issue.

Apart from summaries of held-back notifications, ilert places at most one call to the same phone number every 15 seconds, so that several alerts arriving together cannot ring one phone again and again. A call that falls inside that gap is dropped rather than delayed, and the alert's timeline records that the voice notification was dropped because the temporary rate limit for this target was reached. Calls about an incident have a second limit: at most three to the same person in each 10-minute interval.

To fix or mitigate this issue, follow these steps:

1. **Review Current Alert Volumes:** Check whether there's been an increase in parallel alerts triggering simultaneous calls.
2. **Adjust Escalation Policies:**
   * Add an additional escalation step with a deliberate delay.
   * For example, repeat the previous escalation step after a short interval before escalating to the next higher level.
3. **Evaluate Alert Grouping:** Consider grouping related alerts in your alert sources to reduce the volume of simultaneous alerts and calls.
4. **Verify Implementation:** After adjustments, monitor incoming calls to confirm that alerts escalate appropriately without being unnecessarily discarded.

**Additional Notes:**

* This limit and suppression mechanism were introduced to enhance usability and prevent alert fatigue.
* Every notification limit, for calls, SMS, email, push and messengers, is listed in [How ilert processes events & alerts](/alerting/overview/understanding-event-flows.md#notification-limits).
* If issues persist or you require further customization, reach out to ilert support.


---

# 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.ilert.com/knowledge-base/alerting-and-notifications/why-are-my-ilert-calls-being-discarded-due-to-a-temporary-limit.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.