Error cases supported by assembly catches
Several error cases that can be returned by the assembly are available to the catch function.
- ConnectionError
- An error occurred while establishing a connection to another URL.
- JavaScriptError
- An error occurred while executing JavaScript or GatewayScript in a policy.
- PropertyError
- An error occurred due to an incorrect property during an invoke call or during the execution of a set-variable policy when an action was not set, add, or clear.
- RedactionError
- An error occurred during the redaction of a field as part of a redact policy.
- TransformError
- An error occurred during a transformation policy.
- RuntimeError
- An otherwise unspecified error occurred.
- BadRequestError
- An error occurred while trying to access the request. This is not supported by the default catch; to catch this condition, specify it in your catch definition.
- SOAPError
- A SOAP Fault response was received as the result of a web service invoke request.
- OperationError
- An invoke request received a response with an unsuccessful HTTP status code.
- ValidateError
- An error occurred while trying to schema validate a message payload.
AssemblyRateLimitError- The request exceeds the transaction count threshold specified in the API's Plan.
- UnauthorizedError
- The API cannot be invoked based on the client ID and/or client secret provided, or id/secret were specified in the wrong location. This is not supported by the default catch; to catch this condition, specify it in your catch definition.
- ForbiddenError
- The application making the API request has been disabled or is not active. This is not supported by the default catch; to catch this condition, specify it in your catch definition.