---
alias: user-guide-automation-task-mes-recipeuploadreply
tags:
- automation tasks
description: "Action task that sends the reply back to a pending recipe upload request received from the MES"
---

# Send Recipe Upload Reply

:iot-system-reply-lg:

This **action** task sends the reply back to a recipe upload request received from the MES, completing the request/reply exchange started by the [Recipe Upload Request](task_recipe_upload_request.md) task.

It belongs to the `System / MES` category, under `Actions`.

![Send Recipe Upload Reply - Data Flow Task](./images/send_recipe_upload_reply_task.png)

## Details

| Fields            | Details                                                                            |
| ----------------- | ---------------------------------------------------------------------------------- |
| Scope             | Connect IoT <br> Data Platform <br> Enterprise Integration <br> Factory Automation |
| Workflow          | Data flow                                                                          |
| `IsProtocol` flag | :material-close:{style="color:#EF5350"}                                       |

## Behavior

When activated, this task sends the reply back to the recipe upload request that the [Recipe Upload Request](task_recipe_upload_request.md) task is waiting on, which unblocks the MES. Activating the task confirms the upload. An `Error` on `Failure Reason` reports the upload as failed with its message; any other value confirms the upload.

This task must run in the same workflow branch (`zone`) as the request it answers. If there is no pending request to answer, the task emits `Error` instead.

## Inputs

| Name           | Data Type | Description                                                                       |
| -------------- | --------- | --------------------------------------------------------------------------------- |
| Failure Reason | `Any`     | Optional `Error` reported to the MES when the equipment rejects the recipe upload. Any other value confirms the upload. |
| Activate       | `Any`     | Activates the task, sending the reply.                                            |

Table: Send Recipe Upload Reply task inputs

## Outputs

| Name    | Data Type | Description                                                                        |
| ------- | --------- | ---------------------------------------------------------------------------------- |
| Success | `Boolean` | Triggered when the reply is sent successfully.                                     |
| Error   | `Error`   | Triggered when sending fails, or no pending request exists in the current context. |

Table: Send Recipe Upload Reply task outputs

## Settings

This task has only the usual settings on the `General` tab (Name, Description, and Color).

![Settings Wizard for Send Recipe Upload Reply Task](./images/send_recipe_upload_reply_task_settings.png)

## Remarks

This task pairs with the [Recipe Upload Request](task_recipe_upload_request.md) task, which listens for the request that this task replies to. It must be executed within the `zone` created by that task.

MES confirms the upload with any reply except an error, and records it on the recipe of the **Resource**. To report the upload as failed, link an `Error` with a message into `Failure Reason`: MES adds that message to the feedback of the upload. See [[tutorials-connectiot-mes-interop-scenarios#what-mes-sends-and-expects]].

This task uses a specific structure of context-based data called `zone`. More information on this topic can be read in the [Zones](../zones.md) page.