# 8.5 peinit.critical-service.failed

_Peios / Using Peios / Events / Service Events_

> A service marked Critical failed, and peinit took the machine to its reboot final action.

- **Event type:** `peinit.critical-service.failed`
- **Defined in:** `peinit.evman`
- **Tier:** essential
- **Gating:** none
- **Cardinality:** once per Critical failure that drives the machine to reboot

A service marked Critical failed, and peinit took the machine to its
reboot final action. Essential because it is rare and reboots the machine.

Formerly `critical.failure`.

## 8.5.1 Fields

| Field | Type | Presence | Meaning |
|---|---|---|---|
| [`object.service.name`](/peios/using-peios/events/field-index/fields-object.md#object.service.name) | `str` | required | The name of the service the event is about, as its definition names it. |
| [`outcome.reason`](/peios/using-peios/events/field-index/fields-outcome.md#outcome.reason) | `str.enum` | required | How the Critical service failed.<br><br>Values here (open set): `service-main-terminal` · `health-check-failure` · `watchdog-timeout` · `restart-budget-exhausted`. |
| [`shutdown.finalization-state`](/peios/using-peios/events/field-index/fields-shutdown.md#shutdown.finalization-state) | `str.enum` | required | How far the system shutdown had got when the event was written. |
| [`outcome.detail`](/peios/using-peios/events/field-index/fields-outcome.md#outcome.detail) | `str` | when `shutdown.finalization-state == failed` | Why finalisation failed. |

Every record also carries the header fields of [the envelope](/peios/using-peios/events/introduction/the-envelope.md), which no payload repeats.

*Generated from `peinit.evman` by `pkm/tools/gen-events-book.py`. Edit the fragment, not this page.*