> ## Documentation Index
> Fetch the complete documentation index at: https://docs.larm.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Update disruption

> Updates a disruption — change fields, add a timeline entry, publish to a status page, or resolve

Requires `incidents:read_write` permission.

All fields are optional. A single call can update the title, add a timeline message, publish to a status page, and resolve — all at once.

<ParamField path="id" type="string" required>
  Disruption UUID
</ParamField>

<ParamField body="title" type="string">
  Update the disruption title
</ParamField>

<ParamField body="impact" type="string">
  `minor`, `major`, or `critical`
</ParamField>

<ParamField body="status" type="string">
  Advance the disruption status. Setting to `resolved` or `completed` resolves the disruption.

  Disruption statuses: `investigating`, `identified`, `monitoring`, `resolved`

  Maintenance statuses: `scheduled`, `in_progress`, `completed`
</ParamField>

<ParamField body="message" type="string">
  Adds a timeline entry with this message. If `status` is also provided, the entry reflects the new status.
</ParamField>

<ParamField body="status_page_id" type="string">
  UUID of the status page to publish to. Must be used together with `components`.
</ParamField>

<ParamField body="components" type="object[]">
  Components to mark as affected. Each object has `id` (component UUID) and `status` (`major_outage`, `partial_outage`, `degraded_performance`, `under_maintenance`, or `operational`).
</ParamField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "data": {
      "id": "550e8400-e29b-41d4-a716-446655440000",
      "title": "API outage",
      "type": "disruption",
      "status": "resolved",
      "impact": "major",
      "auto_created": false,
      "started_at": "2026-03-28T12:00:00Z",
      "resolved_at": "2026-03-28T13:00:00Z",
      "updates": [
        {
          "id": "880e8400-e29b-41d4-a716-446655440000",
          "status": "resolved",
          "body": "Issue fixed. All services operational.",
          "posted_at": "2026-03-28T13:00:00Z",
          "posted_by": "user@example.com"
        }
      ],
      "affected_components": [],
      "inserted_at": "2026-03-28T12:00:00Z",
      "updated_at": "2026-03-28T13:00:00Z"
    }
  }
  ```
</ResponseExample>