The REST connector can return errors when input validation fails, connector configuration is incorrect, communication with the REST service cannot be established, or the REST service returns an error response. These errors can be used in process models to identify failures, implement exception handling, and route the process to an appropriate recovery path.
Some errors originate from the connector itself, such as missing or invalid input parameters, while others correspond to HTTP error responses returned by the target REST service.
Note: Many REST connector errors correspond directly to standard
HTTP status codes returned by the target REST service. The exact error returned
depends on the request, connector configuration, and the behavior of the external
service.
The following errors can be returned by the REST connector:
| Error | Description |
|---|---|
| MISSING_INPUT | A required input parameter was not provided. Verify that all mandatory connector inputs are mapped and contain values. |
| INVALID_INPUT | An input parameter contains an invalid value or an unsupported data type. Verify that the input matches the format expected by the connector action. |
| UNKNOWN_ERROR | An unexpected error occurred during connector execution. Review connector configuration, service availability, and application logs for more information. |
| BAD_REQUEST | The REST service rejected the request because it contains invalid or malformed data. This typically corresponds to HTTP status code 400. |
| UNAUTHORIZED | The request could not be authenticated. Verify authentication settings, credentials, API keys, or access tokens. This typically corresponds to HTTP status code 401. |
| FORBIDDEN | Authentication succeeded, but the caller does not have permission to access the requested resource or perform the requested operation. This typically corresponds to HTTP status code 403. |
| NOT_FOUND | The requested endpoint or resource could not be found. Verify the endpoint URL and resource identifiers. This typically corresponds to HTTP status code 404. |
| METHOD_NOT_ALLOWED | The requested HTTP method is not supported by the target endpoint. Verify that the endpoint supports the configured action (GET, POST, PUT, PATCH, DELETE, and so on). This typically corresponds to HTTP status code 405. |
| NOT_ACCEPTABLE | The REST service cannot return data in one of the formats specified by the request. Verify request headers such as Accept. This typically corresponds to HTTP status code 406. |
| PROXY_AUTHENTICATION_REQUIRED | Authentication is required by an intermediary proxy before the request can be processed. This typically corresponds to HTTP status code 407. |
| REQUEST_TIMEOUT | The request was not completed within the allowed time period. Verify service responsiveness and connector timeout settings. This typically corresponds to HTTP status code 408. |
| CONFLICT | The request conflicts with the current state of the target resource. This typically corresponds to HTTP status code 409. |
| GONE | The requested resource is no longer available and has been permanently removed. This typically corresponds to HTTP status code 410. |
| INTERNAL_SERVER_ERROR | The REST service encountered an unexpected condition that prevented it from processing the request. This typically corresponds to HTTP status code 500. |
| NOT_IMPLEMENTED | The REST service does not support the requested functionality or HTTP method. This typically corresponds to HTTP status code 501. |
| BAD_GATEWAY | The service received an invalid response from an upstream service while processing the request. This typically corresponds to HTTP status code 502. |
| SERVICE_UNAVAILABLE | The service is temporarily unavailable or unable to process requests. This typically corresponds to HTTP status code 503. |
| GATEWAY_TIMEOUT | The service did not receive a response from an upstream system within the expected time period. This typically corresponds to HTTP status code 504. |