Class ReasonCode
java.lang.Object
com.sinch.sdk.core.utils.EnumDynamic<String,ReasonCode>
com.sinch.sdk.domains.conversation.models.v1.ReasonCode
Gets or Sets ReasonCode
-
Field Summary
Modifier and TypeFieldDescriptionstatic final ReasonCode
Conversation API validates send requests in two different stages.static final ReasonCode
The configuration of the channel for the used App is wrong.static final ReasonCode
The configuration of the channel is missing from the used App.static final ReasonCode
The channel failed to accept the message.static final ReasonCode
Generic error for channel permanently rejecting a message.static final ReasonCode
The provided Contact ID did not exist.static final ReasonCode
The message or event was rejected by the channel due to a policy.static final ReasonCode
The message delivery, or event delivery, failed due to a channel-imposed timeout.static final ReasonCode
An internal error occurred.static final ReasonCode
The provided media link was not accessible from the Conversation API or from the underlying channels.static final ReasonCode
Some of the referenced media files are too large.static final ReasonCode
Some of the referenced media files is of a unsupported media type.static final ReasonCode
The contact has no channel identities set up, or the contact has no channels set up for the resolved channel priorities.static final ReasonCode
No channels to try to send the message to.static final ReasonCode
No permission to perform action.static final ReasonCode
No available profile data for user.static final ReasonCode
The allowed sending window has expired.static final ReasonCode
The message or event was not sent due to rate limiting.static final ReasonCode
The channel recipient identity was malformed.static final ReasonCode
The contact, or channel recipient identity, has not opt-ed in on the channel.static final ReasonCode
It was not possible to reach the contact, or channel recipient identity, on the channel.static final ReasonCode
Sufficient template parameters was not given.static final ReasonCode
The selected language, or version, of the referenced template did not exist.static final ReasonCode
The referenced template was not found.static final ReasonCode
UNKNOWN is used if no other code can be used to describe the encountered error.static final ReasonCode
The used App is missing.static final ReasonCode
Generic error for channel unsupported operations. -
Method Summary
Modifier and TypeMethodDescriptionstatic ReasonCode
static String
static Stream
<ReasonCode> values()
Methods inherited from class com.sinch.sdk.core.utils.EnumDynamic
equals, hashCode, toString, value
-
Field Details
-
UNKNOWN
UNKNOWN is used if no other code can be used to describe the encountered error. -
INTERNAL_ERROR
An internal error occurred. Please save the entire callback if you want to report an error. -
RATE_LIMITED
The message or event was not sent due to rate limiting. -
RECIPIENT_INVALID_CHANNEL_IDENTITY
The channel recipient identity was malformed. -
RECIPIENT_NOT_REACHABLE
It was not possible to reach the contact, or channel recipient identity, on the channel. -
RECIPIENT_NOT_OPTED_IN
The contact, or channel recipient identity, has not opt-ed in on the channel. -
OUTSIDE_ALLOWED_SENDING_WINDOW
The allowed sending window has expired. See the channel documentation for more information about how the sending window works for the different channels. -
CHANNEL_FAILURE
The channel failed to accept the message. The Conversation API performs multiple retries in case of transient errors. -
CHANNEL_BAD_CONFIGURATION
The configuration of the channel for the used App is wrong. The bad configuration caused the channel to reject the message. Please see the channel support documentation page for how to set it up correctly. -
CHANNEL_CONFIGURATION_MISSING
The configuration of the channel is missing from the used App. Please see the channel support documentation page for how to set it up correctly. -
MEDIA_TYPE_UNSUPPORTED
Some of the referenced media files is of a unsupported media type. Please read the channel support documentation page to find out the limitations on media that the different channels impose. -
MEDIA_TOO_LARGE
Some of the referenced media files are too large. Please read the channel support documentation to find out the limitations on file size that the different channels impose. -
MEDIA_NOT_REACHABLE
The provided media link was not accessible from the Conversation API or from the underlying channels. Please make sure that the media file is accessible. -
NO_CHANNELS_LEFT
No channels to try to send the message to. This error will occur if one attempts to send a message to a channel with no channel identities or if all applicable channels have been attempted. -
TEMPLATE_NOT_FOUND
The referenced template was not found. -
TEMPLATE_INSUFFICIENT_PARAMETERS
Sufficient template parameters was not given. All parameters defined in the template must be provided when sending a template message. -
TEMPLATE_NON_EXISTING_LANGUAGE_OR_VERSION
The selected language, or version, of the referenced template did not exist. Please check the available versions and languages of the template. -
DELIVERY_TIMED_OUT
The message delivery, or event delivery, failed due to a channel-imposed timeout. See the channel support documentation page for further details about how the different channels behave. -
DELIVERY_REJECTED_DUE_TO_POLICY
The message or event was rejected by the channel due to a policy. Some channels have specific policies that must be met to send a message. See the channel support documentation page for more information about when this error will be triggered. -
CONTACT_NOT_FOUND
The provided Contact ID did not exist. -
BAD_REQUEST
Conversation API validates send requests in two different stages. The first stage is right before the message is enqueued. If this first validation fails the API responds with 400 Bad Request and the request is discarded immediately. The second validation kicks in during message processing and it normally contains channel specific validation rules. Failures during second request validation are delivered as callbacks toMESSAGE_DELIVERY (EVENT_DELIVERY)
webhooks with ReasonCodeBAD_REQUEST
. -
UNKNOWN_APP
The used App is missing. This error may occur when the app is removed during message processing. -
NO_CHANNEL_IDENTITY_FOR_CONTACT
The contact has no channel identities set up, or the contact has no channels set up for the resolved channel priorities. -
CHANNEL_REJECT
Generic error for channel permanently rejecting a message. Only used if no other better matching error can be used. -
NO_PERMISSION
No permission to perform action. -
NO_PROFILE_AVAILABLE
No available profile data for user. -
UNSUPPORTED_OPERATION
Generic error for channel unsupported operations.
-
-
Method Details
-
values
-
from
-
valueOf
-