Error type IDs

Error type IDs enable consistent error detection and response without parsing unstructured messages. Recipes use error type IDs to group related failures or target specific cases.

Structured HTTP error responses

The HTTP connector currently exposes error_type_id with related http_response fields. Refer to Error handling with the HTTP connector for more information.

Workato exposes the following fields in supported job errors:

Field	Description
error_type_id	Stable identifier for the error type. For example: err.http.response.client_error.not_found.
error_type	Display name for the error. For example: Not Found.
error_id	Unique identifier for the specific error instance.
error_message	High-level summary of what occurred.
http_response	Structured data including status code, headers, and body.

You can use error_type_id in Monitor actions for error blocks to detect specific failures and define how recipes respond. This improves reliability because recipe logic uses a stable identifier.

Example payload

The job error includes structured fields you can reference with the identifier. For example:

{
  "error_type_id": "err.http.response.client_error.not_found",
  "error_type": "Not Found",
  "error_id": "abc123-xyz",
  "error_message": "HTTP 404 error",
  "http_response": {
    "protocol_version": "HTTP/1.1",
    "code": 404,
    "status_text_exact": "NOT FOUND",
    "status_text": "Not Found",
    "headers": {
      "Content-Type": "application/json"
    },
    "body": "{\"error\": \"Resource not found\"}"
  }
}

HTTP error categories

The HTTP connector defines structured error_type_ids for both connection-level and response-level issues.

Connection-level errors

These identifiers represent errors raised before a response status code is returned.

Error	error_type_id	Description
Generic HTTP error	err.http.response.*	General HTTP request failure not tied to a specific status code.
HTTP timeout	err.http.response.timeout	Request timed out before receiving a response.
Transient API server error	err.http.response.transient_error	Temporary server or network issue that may succeed on retry.

Response-level errors

Once the connector receives a response from the server, error_type_ids map to HTTP status classes.

HTTP status class	error_type_id prefix	Description
3xx	err.http.response.redirection.*	Redirection responses.
4xx	err.http.response.client_error.*	Client-side errors such as 404 or 401.
5xx	err.http.response.server_error.*	Server-side errors such as 500 or 503.

Data format errors {: #data-format-errors }

These identifiers represent data serialization or parsing failures when transforming or reading payloads.

Error	error_type_id	Description
Avro serialization error	err.data_format.avro_serialization_error	Error encoding or decoding Avro data.
CSV parsing error	err.data_format.csv_parsing_error	Error parsing CSV content due to malformed structure or invalid delimiter.
JSON parsing error	err.data_format.json_parsing_error	Error parsing JSON payload due to invalid format or unescaped character.
XML parsing error	err.data_format.xml_parsing_error	Error parsing XML payload due to invalid tag or schema mismatch.