Distributed Message Send#
The task Distributed Message Send sends distributed messages with a structured request-response mechanism. It ensures message delivery, retries on failure, and processes replies within a specified timeout.
Details#
| Fields | Details |
|---|---|
| Scope | Connect IoT Factory Automation Enterprise Integration Data Platform |
| Workflow | Data flow Control flow |
IsProtocol flag |
Inputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| Id | string | If provided is used as request ID | |
| Data | Object | The payload of the distributed Message | |
| Activate | Any | Activates the task execution |
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| data | any | The data sent back by the receiver | |
| Id | any | The same Id used for the request | |
| Success | Boolean | If there was no problem emits a true | |
| Error | Error | Error that occurred during the processing of this task |
Settings#
On the General Tab, you have the usual settings and the following options settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Service Name | string | Defines the target service for the distributed message | ||
| Request Timeout | Integer | Determines the maximum time (in seconds) the task will wait for a reply after sending a distributed message. | ||
| Attempts | Integer | Defines the maximum number of times the task will retry sending a distributed message if the initial attempt fails. | ||
| Sleep between attempts | Integer | Defines how long (in milliseconds) the task waits between retry attempts when sending a distributed message fails. | ||
| Confirmation Timeout | Integer | Maximum time (in seconds) the task waits for an acknowledgment after sending a distributed message. |
Behavior#
If you provide an id input, it will be used as the unique identifier for the message being sent. If the id is not passed, the task will generate an id using either a job ID (_jobId) from the context (if available) or generate a new unique identifier (UUID). The task retries sending the message if needed, based on the configured number of attempts and sleep time between retries. If a response is received, the task outputs the received data and Id. If no reply arrives within the timeout, it logs an error.