*Workflows › Reference › Actions › Maintenance*

# Update incident

> Updates an existing incident: status, priority, affected resource, dates and costs.

## At a glance

| Property | Value |
| --- | --- |
| Domain | `incidents` |
| Group in the editor | Maintenance › Incidents |
| Runs as | The owner of the workflow, with their permissions |
| Permission | Edit access to Incidents. Administrators always pass; a module outside the plan blocks everyone. |
| Add-on | Maintenance |
| Destructive | No: the public MCP catalogue does not mark it as destructive |
| Also available in | REST API, MCP (`filmo_incidents_update`) |

ACTION `incidents.update`

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `incidentId` | string | Yes | Incident |
| `title` | string | No |  |
| `type` | enum<string> | No | Incident type `damage`, `loss`, `malfunction`, `cosmetic`, `theft`, `custom` |
| `description` | string | No |  |
| `status` | enum<string> | No |  `draft`, `open`, `waiting`, `repairing`, `complete`, `lost` |
| `priority` | enum<string> | No | How urgently it has to be handled. `urgent`, `high`, `medium`, `low`, `none` |
| `severity` | enum<string> | No | The incident's impact. With «High» it appears in the escalation views. `low`, `high` |
| `repairType` | enum<string> | No | Internal if you repair it yourselves; external if it is sent to a supplier. `internal`, `external` |
| `blocksAvailability` | boolean | No | While the incident is open, the resource cannot be reserved on new orders. |
| `affectedQuantity` | number | No | How many units of the item are affected. Only for bulk items. |
| `assigneeStaffIds` | string[] | No | Owners |
| `dueDate` | string | No | Deadline |
| `estimatedResolutionDate` | string | No |  |
| `actualResolutionDate` | string | No |  |
| `reminderDate` | string | No |  |
| `estimatedCost` | number | No | Estimated repair cost |
| `actualCost` | number | No | Actual repair cost |
| `chargeToClient` | boolean | No | The cost will be passed on to the customer on the source order. |
| `orderId` | string | No | **Source order.** The order in which it was detected. If you give it, the incident inherits that order's project. |
| `projectId` | string | No | Project |

## Outputs

| Name | Type | Description |
| --- | --- | --- |
| `incidentId` | string |  |
| `status` | string |  |

---

Canonical URL: https://docs.filmo.io/workflows/reference/actions/incidents-update  
Last updated: 2026-10-25