---
title: "uptimeify_im_escalation_tier"
description: "Ressource uptimeify_im_escalation_tier: Beispiel, alle Attribute, Import."
---

<Callout>Die Beschreibungen auf dieser Seite kommen direkt aus dem Provider-Schema und sind deshalb englisch.</Callout>

An escalation tier of an Incident Management team. Creating a tier also creates its default schedule (`default_schedule_id`, rotation mode `none`) whose single rotation is `member_user_ids`; further schedules of the tier are `uptimeify_im_schedule`. Import with `<team_id>/<tier_id>`.

## Beispiel

```terraform
resource "uptimeify_im_escalation_tier" "first" {
  team_id                       = uptimeify_im_team.platform.id
  tier_order                    = 1
  member_user_ids               = [uptimeify_im_team_member.alice.user_id]
  auto_escalation_after_minutes = 10
  auto_escalation_severities    = ["critical", "warning"]

  # Escalate automatically only on weekdays, office hours.
  auto_escalation_time_filters = [
    { from = "08:00", until = "18:00", days = [1, 2, 3, 4, 5] },
  ]
}

resource "uptimeify_im_escalation_tier" "second" {
  team_id         = uptimeify_im_team.platform.id
  tier_order      = 2
  member_user_ids = [uptimeify_im_team_member.bob.user_id]
}
```

## Schema

### Pflichtfelder

- `member_user_ids` (List of String) Team members on the default schedule's rotation, in order (1 to 200 user ids). Changing it replaces all rotation groups of the default schedule.
- `team_id` (Number)

### Optional

- `auto_escalation_after_minutes` (Number) Minutes before escalating to the next tier. Default `5`.
- `auto_escalation_enabled` (Boolean) Default `true`.
- `auto_escalation_severities` (Set of String) Severities that escalate: `critical`, `warning`, `minor`. Unset = all.
- `auto_escalation_stop_mode` (String) `acknowledged` or `resolved`. Default `acknowledged`.
- `auto_escalation_time_filters` (Attributes List) Weekly windows in which auto-escalation runs. Empty (default) = always. (siehe [verschachteltes Schema](#verschachteltes-schema-für-auto_escalation_time_filters))
- `repeats` (Number) Extra pages on this tier before moving on. Default `0`.
- `repeats_after_minutes` (Number) Minutes between repeats; unset = `auto_escalation_after_minutes`.
- `repeats_stop_mode` (String) `acknowledged` or `resolved`. Default `acknowledged`.
- `tier_order` (Number) Position in the team's ladder, 1 = paged first. Unset = appended at the end. On create the tier is inserted there (tiers at or after it move down by one); a later change reorders the team's tiers (POST .../tiers/reorder). Both move the other tiers too: when you set it, set it on every tier of the team, as 1..n. A value larger than the number of tiers ends up as the last position.

### Nur lesbar

- `default_schedule_id` (Number) Schedule the API created with the tier. Do not also manage it as `uptimeify_im_schedule`.
- `id` (String) `<team_id>/<tier_id>`.
- `tier_id` (Number) Numeric tier id.

### Verschachteltes Schema für `auto_escalation_time_filters`

Required:

- `days` (List of Number) ISO weekdays, 1 = Monday to 7 = Sunday.
- `from` (String) `HH:mm`.
- `until` (String) `HH:mm` or `24:00`.

## Import

Import geht so:

Mit [`tofu import` bzw. `terraform import`](https://developer.hashicorp.com/terraform/cli/commands/import), zum Beispiel:

```shell
# <team_id>/<tier_id>
terraform import uptimeify_im_escalation_tier.first 12/56
```