200-299 Asynchronous Operation

Error	Message	Resolution
200	CallsInConversation don't match previous value in the Conversation. Conversation has been invalidated	All conversation parts of a conversation must specify the same value for CallsInConversation. The error is returned when one or more conversation part has a CallsInConversation value that does not match the first conversation part CallsInConversation value. Set all Options.CallsInConversation to the same value equal to the total number of conversation parts for the conversation.
201	Async API Collection Total Mismatch
202	Missing Required Conversation Property SequenceCode. ConversationID, SequenceCode, and CallsInConversation are required for Conversations Requests	SequenceCode has not been specified in the Options object for the Request. SequenceCode is a required property for conversation requests that specify a CallsInConversation, ConversationID, and RequestType == Asynchronous. SequenceCode is not required if the CallsInConversation is not specified. SequenceCode and CallsInConversation default to 1 when not provided and the request is interpreted as a single-part conversation. For multi-part Conversations, SequenceCode is required and must be a sequential whole number starting with 1. If the request is intended to be asynchronous, then set the SequenceCode value to an integer greater than 0. If the request is not intended to be asynchronous, then check that none of the asynchronous conditions below are true: Options.RequestType == Asynchronous Options.ConversationID is specified Options.SequenceCode is specified Options.CallsInConversation is specified hese conditions indicate that the call is intended to be asynchronous. Don't specify any of these properties for synchronous calls.
203	Async API Timeout	The status of the conversation context timed out. Ensure you use a current and correct conversation in your calls.
204	Async API Error	The object being created, updated, or deleted failed validation. Ensure you use a valid object in your code.
205	SequenceCode Out Of Bounds. Valid SequenceCode range is 1 to the value of CallsInConversation	The SequenceCode denotes the sequential order to process the conversation parts. The application returns this error when the SequenceCode value is greater than the CallsInConversation value. Set SequenceCode to an integer greater than zero and less than CallsInConversation.
206	CallsInConversation Out Of Bounds. CallsInConversation is expected to be a positive number	Set Options.CallsInConversation to an integer greater than zero.
207	Missing Required Conversation Property ConversationID. ConversationID, SequenceCode, and CallsInConversation are required for Conversations Requests	ConversationID has not been specified in the Options object for the request or the value is null or string.Empty. If the request is intended to be asynchronous, that request requires a unique ConversationID per conversation. Set Options.ConversationID to a string value other than null or string.Empty. If the request is not intended to be asynchronous, then check that none of the asynchronous conditions below are true: Options.RequestType == Asynchronous Options.ConversationID is specified Options.SequenceCode is specified Options.CallsInConversation is specified These conditions indicate that the call is intended to be asynchronous. Don't specify any of these properties for synchronous calls.
208	Missing Required Conversation Property CallsInConversation. ConversationID, SequenceCode, and CallsInConversation are required for Conversations Requests	CallsInConversation has not been specified in the Options object for the request. CallsInConversation is a required property for conversation requests that specify a SequenceCode, ConversationID, and RequestType == Asynchronous. CallsInConversation is not required if the SequenceCode is not specified. SequenceCode and CallsInConversation default to 1 when not provided and the request is interpreted as a single-part conversation. For multi-part conversations, CallsInConversation is required, must be an integer greater than 0, and must equal the number of total conversation parts. Set CallsInConversation to a whole number integer greater than 0 equal to the number of total conversation parts. If the request is not intended to be asynchronous, then check that none of the asynchronous conditions below are true: Options.RequestType == Asynchronous Options.ConversationID is specified Options.SequenceCode is specified Options.CallsInConversation is specified These conditions indicate that the call is intended to be asynchronous. Don't specify any of these properties for synchronous calls.
209	Options.RequestType is required to be set to RequestType.Asynchronous	Set Options.RequestType to RequestType.Asynchronous. If the request is not intended to be asynchronous, then check that none of the asynchronous conditions below are true: Options.RequestType == Asynchronous Options.ConversationID is specified Options.SequenceCode is specified Options.CallsInConversation is specified These conditions indicate that the call is intended to be asynchronous. Don't specify any of these properties for synchronous calls.
211	Invalid ConversationID. ConversationID has already been used	ConversationIDs are unique per client and cannot be reused. This error is returned when a client attempts to reuse a ConversationID. This includes conversations that have timed out or have produced an error condition. If the conversation has multiple parts, then each part has to use the same ConversationID. Set Options.ConversationID to a unique value for each set of conversations.
212	Invalid Conversation	This general error indicates an unspecified problem with a conversation. The conversation does not contain a Closed, Processing, Error, Complete, or Timeout status. Contact the Global Support team.
213	Conversation is in an error state and is no longer able to accept conversation parts	When a conversation is in an error state, any conversation parts for a given ConversationID return this message. The close conversation may not provide a valid conversation ID or may encounter an SQL error. Review previous responses, locate the initial error, and fix. Resubmit the entire conversation with a new ConversationID.
214	SequenceCode already used for Conversation. Conversation has been invalidated	SequenceCodes within a conversation are unique. Once a conversation part has been accepted with a particular SequenceCode, that value cannot be repeated in the conversation. This is considered a fatal error that results in the conversation being in an error state. Set Options.SequenceCodes in all conversation parts to sequential values starting with 1 and ending with the same value that is set in Options.CallsInConversation. Resubmit the entire conversation with a new ConversationID.
215	Conversation is closed and cannot accept more parts	Conversations are closed and ready for processing once all parts have been received. Once a conversation is closed, no new parts are accepted. This error is informational and no action is required unless you intended for the rejected part to be part of the closed conversation. In this case, the proper course of action depends on the circumstances surrounding the conversation.
218	Too many objects	Use fewer than 32,767 API objects in your request.
226	A request may not have ScheduledTime greater than 30 days from now	Schedule your conversation and non-conversation messages 30 days or fewer in the future.
227	An unsecure response address specified in the 'SendResponseTo' parameter.	Use an HTTPS endpoint for HTTP callbacks. After the July 2020 release, new customers can’t send callbacks from the Async API to unsecured HTTP endpoints.