The possible errors that can be handled by the Transcribe connector are:
Error | Description |
---|---|
MISSING_INPUT | A mandatory input variable was not provided. |
INVALID_INPUT | The input variable has an invalid type. |
INVALID_RESULT_FORMAT | The REST service result payload cannot be parsed. |
LIMIT_EXCEEDED | The service limit was exceeded. |
ACCESS_DENIED | The user is not authorized to perform the action. |
INTERNAL_FAILURE | An internal Amazon Lex error occurred. |
UNKNOWN_ERROR | An unexpected runtime error occurred. |
BAD_REQUEST | The server could not understand the request due to invalid syntax. |
UNAUTHORIZED | The request has not been applied because it lacks valid authentication. |
FORBIDDEN | The server understood the request but refused to authorize it. |
NOT_FOUND | The server could not find what was requested. |
METHOD_NOT_ALLOWED | The request method is known by the server but is not supported. |
NOT_ACCEPTABLE | The server cannot produce a response matching the list of acceptable values. |
REQUEST_TIMEOUT | The server is requesting to shut down this unused connection. |
CONFLICT | The request conflicts with the current state of the server. |
GONE | No longer available. |
UNPROCESSABLE_ENTITY | The server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions. |
LOCKED | The resource that is being accessed is locked. |
FAILED_DEPENDENCY | The request failed due to failure of a previous request. |
INTERNAL_SERVER_ERROR | The server has encountered a situation and does not know how to handle it. |
NOT_IMPLEMENTED | The request method is not supported by the server and cannot be handled. |
BAD_GATEWAY | The server got an invalid response. |
SERVICE_UNAVAILABLE | The server is not ready to handle the request. |
GATEWAY_TIMEOUT | The server is acting as a gateway and cannot get a response in time. |