AWS Amazon Connect Error Codes

You do not have sufficient permissions to perform this action.

Request processing failed because dependent condition failed.

Operation cannot be performed at this time as there is a conflict with another operation or contact state.

The flow has not been published.

The contact with the specified ID does not exist.

Outbound calls to the destination number are not allowed.

A resource with the specified name already exists.

An entity with the same name already exists.

Request processing failed because of an error or failure with the service.

This exception occurs when an API request is made to a non-active region in an Amazon Connect instance configured with Amazon Connect Global Resiliency. For example, if the active region is US West (Oregon) and a request is made to US East (N. Virginia), the exception will be returned.

The flow is not valid.

The problems with the module. Please fix before trying again.

One or more of the specified parameters are not valid.

The request is not valid.

The test is not valid.

The allowed limit for the resource has been exceeded.

Maximum number (1000) of tags have been returned with current request. Consider changing request parameters to get more tags.

The contact is not permitted.

Thrown for analyzed content when requested OutputType was not enabled for a given contact. For example, if an OutputType.Raw was requested for a contact that had `RedactedOnly` Redaction policy set in the flow.

The property is not valid.

A resource already has that name.

That resource is already in use (for example, you're trying to add a record with the same name as an existing record). If you are trying to delete a resource (for example, DeleteHoursOfOperation or DeletePredefinedAttribute), remove its reference from related resources and then try again.

The specified resource was not found.

The resource is not ready.

The service quota has been exceeded.

The throttling limit has been exceeded.

Displayed when rate-related API limits are exceeded.

No user with the specified credentials was found in the Amazon Connect instance.