Unhandled Error#
The Unhandled Error Task creates a handler that will capture any error message generated by the system, regardless of there being any other error-handling mechanism attached to any output of an existing Task. This is useful to avoid having multiple handlers on each of the Error outputs of the tasks and can be used by anyone that does not want to handle minor issues but still might want to investigate the source of those issues.
Inputs#
| Name | Data Type | Description |
|---|---|---|
| Activate | any | Log the value defined in message input |
Outputs#
| Name | Data Type | Description |
|---|---|---|
| errorSourceId | String | Source ID of the error message |
| errorSource | String | Source of the error message |
| errorPage | String | |
| errorReceived | Object | Received message content |
| Success | Boolean | If there was no problem emits a true |
| Error | Error | Error that occurred during the processing of this task |
Settings#
| Name | Data Type | Value | Default | Description |
|---|---|---|---|---|
| Auto activate | Boolean | true | whether the task should receive unhandled errors as soon as it is started |
Behavior#
Whenever the Activate inputs receive a value (or in case of AutoActivate being true, from the moment the workflow is started), any error that is not handled by an existing block will be received and emitted by this task.
When an error output or an exception is thrown on a converter, if no link is defined on the error output, it should be sent to this special global error handling.
Attaching a Log Message block to the error outputs of this task will allow easy error logging and permit further investigation of any potential problem without hindering the execution of the workflow.
Note
If the task that generated the error has an error port and a link to it, the error is considered handled and therefore not caught by this task.
Remarks#
None.