# Reassign an Incident's Service

Replaces an incident's impacted service with a different one, which also updates the incident's escalation policy and responders.


> **Availability:** See the [Incident Workflow Actions Overview table](/workflow-actions) for the plans this workflow is available on.

## Description

Update which service is marked as impacted on an existing incident. Use this to correct mis-triage or transfer ownership when the wrong service was selected.

- **What it does**: Replaces the incident’s current impacted service with the one you specify. When an incident is reassigned to another Service, the associated Escalation Policy and responders _are also updated_.
- **What it doesn’t do**: It does not change incident priority.

## Instructions

1. If you have not done so, follow the instructions to [Create an Incident Workflow](/ai-automation/automation/incident-workflows#create-an-incident-workflow).
2. When the instructions prompt you to [add actions](/ai-automation/automation/incident-workflows#add-actions), select **this action**.
3. Enter the following **Inputs** and click **Save**.
4. Continue following instructions to **Publish** the Workflow.
5. When the action runs, you will see the **Outputs** listed below.

## Inputs

> **Field References:** Fields with the **\{+\}** icon accept [Field References](/ai-automation/automation/incident-workflows#field-references), which can be useful for referencing incident data or outputs created in prior workflow steps. To add Field References, click **\{+\}**, or enter `{{`, and select relevant fields. Refer to the [Field References](/ai-automation/automation/incident-workflows#field-references) article for more information.

<br />

| Name             | Description                                                                                                                         |
| :--------------- | :---------------------------------------------------------------------------------------------------------------------------------- |
| Incident ID      | ID of the incident to be edited                                                                                                     |
| Impacted Service | The ID or name of the impacted service                                                                                              |
| User ID          | The ID of the user who is assigned to the incident. **Note**: If multiple users are assigned, the ID of the first user will be used |

## Outputs

| Name           | Description                                                                         |
| :------------- | :---------------------------------------------------------------------------------- |
| Result         | Value that shows if the action was successful or not. Either "Success" or "Failed." |
| Result Summary | Brief description of what the action did or if it failed                            |
| Error          | Brief description that populates if the action failed                               |

<br />

> **Tips:** - Ensure the incident and service both exist and are accessible in your account.
> - If the selected service matches the current impacted service, the action will be treated as a no-op.
> - The impacted service can be selected from the dropdown list _or_ by entering its ID directly.