---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Execute remedial action subflow inputs and outputs

# Execute remedial action subflow inputs and outputs {#ariaid-title1}

Release version: Brazil  
Updated October 23, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The Execute remedial action subflow runs a DEX remedial action on a device. The subflow takes inputs, returns outputs and messages, and doesn't run when certain conditions apply.

## Inputs {#execute-remedial-action-subflow-reference__section-inputs}

The following table describes the inputs that you provide to the Execute remedial action subflow. For the procedure, see [Execute remedial action subflow](https://www.servicenow.com/docs/6j7Pbdo_pt_HGParua0KOQ "Use the Execute remedial action subflow to run a DEX remedial action on a device, and test it in Workflow Studio.").
{#execute-remedial-action-subflow-reference__table-subflow-inputs__entry__3}

| Input | Required | Description |
|-|-|-|
| device_id | Yes | The sys_id of the computer CI (`cmdb_ci_computer`) of the device to run the remedial action on. |
| remedial_action_id | Yes | The sys_id of the remedial action (`sn_reacf_remedial_action`) to run. |
| action_params | Yes | A JSON object that maps the column name---not the label---of each remedial action parameter to its value. If the remedial action has no parameters, enter `{}`. |
| origin_sys_id | No | The sys_id of the remedial action origin (`sn_reacf_remedial_action_origin`). The origin is used to track the run in the remedial action execution record. |
[ ]

{#execute-remedial-action-subflow-reference__table-subflow-inputs}

## Outputs {#execute-remedial-action-subflow-reference__section_mkl_jh5_5kc}

{#execute-remedial-action-subflow-reference__table_nkl_jh5_5kc__entry__2}

| Output | Description |
|-|-|
| status_code | The result of the run: * Success (the remedial action ran and the subflow received its result) * Failed (the subflow didn't run the remedial action---see conditions that stop a run) * Timeout (the remedial action started, but the subflow stopped waiting for the result after 15 minutes) {#execute-remedial-action-subflow-reference__ul_b1g_yh5_5kc} |
| error_message | The message that explains a Failed or Timeout result. For details, see [Messages](https://www.servicenow.com/docs/YXzM1rJhM~JeffME9qoG2Q#execute-remedial-action-subflow-reference__section-messages). |
| output | A JSON object with the details of the run, including the parameters used, the message, and the status that the device reported. |
[ ]

{#execute-remedial-action-subflow-reference__table_nkl_jh5_5kc}

## Conditions that stop a run {#execute-remedial-action-subflow-reference__section-failure-conditions}

The subflow doesn't run the remedial action when any of the following conditions apply:

* The remedial action ID isn't valid, or the remedial action is inactive.
* The device ID isn't valid.
* The remedial action isn't supported for the operating system of the device.
* The device is offline.
* The action parameters aren't valid.

## Messages {#execute-remedial-action-subflow-reference__section-messages}

The following table describes the messages that the subflow can return.
{#execute-remedial-action-subflow-reference__table-subflow-messages__entry__2}

| Message | Meaning |
|-|-|
| Remedial action completed successfully. | The remedial action finished on the device. |
| Remedial action failed to execute. | The remedial action ran on the device but failed. |
| Remedial action was cancelled. | The remedial action was cancelled before it finished. |
| Target device is not reachable (offline). Remedial action can't be executed on an offline device. | The device was offline, so the subflow didn't run the remedial action. |
| Remedial action triggered successfully but execution monitoring timed out. | The subflow started the remedial action but stopped waiting for the result after 15 minutes. |
| Remedial action is not available. It may be inactive or the provided ID is invalid. Verify the remedial action configuration and try again. | The remedial action ID is not valid, or the remedial action is inactive. |
| Remedial action is not supported for the target device's operating system. | The remedial action doesn't support the operating system of the device. |
[ ]

{#execute-remedial-action-subflow-reference__table-subflow-messages}

For status values, see [Outputs](https://www.servicenow.com/docs/YXzM1rJhM~JeffME9qoG2Q#execute-remedial-action-subflow-reference__section_mkl_jh5_5kc).