This is the XML format of an error response returned when a [Message Start Event (HTTP)] or [Receive Task (HTTP)] results in an error.
BPMN Icon: [Message Start Event (HTTP)], [Receive Task (HTTP)]
XML Format for an error
The HTTP response code for errors is 400, and the error message is returned in XML (text/xml) in the following format
<message-start-event-errors>
<error>
<key>…</key>
<detail>…</detail>
</error>
…
</message-start-event-errors>- <message-start-event-errors>: Message Start Event (HTTP)
- <receive-task-errors>: Receive Task (HTTP)
- <key>: The type of error
- For Data Items validation errors, the parameter name is displayed
- <detail>: detailed information used to identify the cause of the error
- For Data Items validation errors, it will be the same as the error message in the form
- For other errors, the input value that caused the error may be displayed as-is
Error types and Notification destination
Depending on the type of error, an error notification email will be sent to the following notification destination.
| Person to be Notified | Error Types |
|---|---|
| System Administrator | No parameter, no integer in processModelInfoId, processInstanceId, nodeNumber |
| No Workflow App of specified processModelInfoId | |
| Case Manager | No node of specified nodeNumber |
| Specified Workflow App not active | |
| Specified node is not Message Start Event node | |
| Parameter name error | |
| Has reached the limit in the number of Cases | |
| Data variation error (i.e., text in numeric type) | |
| Required data is not filled |