# Repeat escalations

### Basics of repeating escalation policies

Repeat your escalation policy a.k.a keep alerts going from the top if none of the members invovled in the policy take any action for an incident.

Let's take a simple example. Consider the below policy.

When a new incident is created -

**Step 1:** Alert on #incidents Slack channel

**Step 2:** Email Jay Ramirez

**Step 3:** Phone call to Jay Ramirez

![Example escalation policy](/files/-MI2v79cTkmbE4KG_cWg)

In this case, if noone on the Slack channel takes an action and Jay also misses out on it, then the alerts will continue from **Step 1 after a default interval of 10 minutes.**

This is handy as some incidents can just not be ignored.

{% hint style="info" %}
To avoid alert fatigues, escalation policy will only be repeated 5 times.
{% endhint %}

### How to setup repeating escalations?

At Spike.sh, you can choose to configure repeating escalations on an integration basis and not on a central level. We designed this so you can choose exactly which integrations are critical to never miss an alert.

To setup, you can configure this while adding or editing an integration. Select **Repeat escalation checkbox** and save / update integration.

![Configure repeat escalations for any integration](/files/-MI2xYjsqMLiTOMsEXhX)

### What actions would stop from repeating escalations?

If you **acknowledge or resolve** an incident then escalations will stop repeating itself and alerts will stop automatically.

{% content-ref url="/pages/-Ln7Jxx-MbPRgKiIKLTu" %}
[How to change incident status?](/incidents/how-to-change-incident-status.md)
{% endcontent-ref %}

### If no action is taken, wouldn't the escalations repeat continuously?

This is a valid problem. For this reason, by default, **we repeat escalations 5 times**. After which, no alerts will be sent.


---

# Agent Instructions: 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:

```
GET https://docs.spike.sh/escalations/repeat-escalations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.