---
alias: user-guide-automation-task-opcua-commandresult
tags:
- automation tasks
description: "This task delivers OPC UA method results, including success and error status, for OnCommand tasks"
---

# Command Result

![Screenshot showing a command result display.](images/commandresult-lg.svg)

This task returns the result of an OPC UA method call. To be used together with the OnCommand task.

![Screenshot showing a command result with parameters.](./images/command_result_parameters.png)

!!! warning
    This task is currently deprecated and will be removed in future versions.

## Inputs

| Name    | Data Type | Values | Description                                                                            |
|---------|-----------|--------|----------------------------------------------------------------------------------------|
| Id      | `Object`  |        | Unique identifier of the request (from the OnCommand task) to which the results relate |
| Success | `Boolean` |        | Result of the method execution                                                         |
| Error   | `Error`   |        | Used to report an error in the method execution                                        |

## Outputs

None.

## Settings

On the *General Tab*, you have the usual settings and the following settings:

| Name    | Data Type | Default | Description  |
| ------  | --------- | --------- | --------- |
| Automation Command | `AutomationCommand` |  |  The command to send |
| Expiration Time | `Integer` |  |  Expiration time for the command (in milliseconds) |

![Screenshot showing a settings page with options for general results.](./images/command_result_settings.png)

On the *Results* Tab, you have entries for each of the result parameters of the command:

![Screenshot showing a settings page with options for command result settings.](./images/command_result_settings_results.png)

## Behavior

Select a command (corresponding to a OPC UA method) to reply to and the task inputs will be generated based on the respective output arguments.

The task will send a reply to the driver with the input values once it receives either a success or an error value.

Values received in the inputs are stored by execution context.

## Remarks

None.