200–299 Asynchronous Operation

ErrorMessageResolution
200CallsInConversation don’t match previous value in the Conversation. Conversation has been invalidatedThe error is returned when one or more conversation parts have a CallsInConversation value that doesn’t match the value specified in the first conversation part. Set CallsInConversation to the same value in all conversation parts. The value that you specify must equal the total number of conversation parts for the conversation.
201Async API Collection Total Mismatch
202Missing Required Conversation Property SequenceCode. ConversationID, SequenceCode, and CallsInConversation are required for Conversations RequestsSequenceCode isn’t specified in the Options object for the Request. SequenceCode is a required property for conversation requests that specify a value for CallsInConversation or ConversationID, or that specify a RequestType of Asynchronous.

If CallsInConversation isn’t specified, then SequenceCode isn’t required. SequenceCode and CallsInConversation default to 1 when not specified in a request, which causes the conversation to be created as a single-part conversation. For multi-part conversations, specify a value for SequenceCode, with the first message in the conversation having a value of 1.

If the request is intended to be asynchronous, set the SequenceCode value to an integer greater than or equal to 1.
203Async API TimeoutThe conversation context timed out. Ensure that you’re using a current and correct conversation ID in your calls.
204Async API ErrorThe object being created, updated, or deleted failed validation. Check the object syntax and structure in your code.
205SequenceCode Out Of Bounds. Valid SequenceCode range is 1 to the value of CallsInConversationThe SequenceCode denotes the sequential order to process the conversation parts. The application returns this error when the value of SequenceCode is greater than the value of CallsInConversation . Set SequenceCode to an integer greater than or equal to 1 and less than or equal to the value of CallsInConversation.
206CallsInConversation Out Of Bounds. CallsInConversation is expected to be a positive numberSet Options.CallsInConversation to an integer greater than or equal to 1.
207Missing Required Conversation Property ConversationID. ConversationID, SequenceCode, and CallsInConversation are required for Conversations RequestsConversationID isn’t specified in the Options object or its value is null.

If the request is intended to be asynchronous, that request requires a unique value for ConversationID. Set Options.ConversationID to a non-null string value.
208Missing Required Conversation Property CallsInConversation. ConversationID, SequenceCode, and CallsInConversation are required for Conversations RequestsCallsInConversation hasn’t been specified in the Options object for the request. CallsInConversation is a required property for conversation requests that specify a SequenceCode, ConversationID, and that have a RequestType value of Asynchronous.

If you didn’t specify a SequenceCode in the request, then CallsInConversation isn’t required.

If you don’t provide values for SequenceCode and CallsInConversation, they both default to 1 and the request is interpreted as a single-part conversation.

For multi-part conversations, you must specify a CallsInConversation value that is greater than or equal to 1, and that equals the total number of conversation parts.
209Options.RequestType is required to be set to RequestType.AsynchronousSet Options.RequestType to RequestType.Asynchronous.
211Invalid ConversationID. ConversationID has already been usedConversation IDs can’t be reused. This error is returned when a ConversationID is reused, even if the conversations associated with the existing ID have timed out or produced an error. If the conversation has multiple parts, then each part must use the same ConversationID. Set the value of ConversationID to a unique value for each set of conversations.
212Invalid ConversationThis general error indicates an unspecified problem with a conversation. The conversation doesn’t have a status of Closed, Processing, Error, Complete, or Timeout. Contact Global Support for help.
213Conversation is in an error state and is no longer able to accept conversation partsWhen a conversation is in an error state, all conversation parts for its ConversationID return this message. Closing the conversation results in an error.

Review the previous responses, locate the error, fix it, and then resubmit the entire conversation with a new ConversationID.
214SequenceCode already used for Conversation. Conversation has been invalidatedSequenceCodes within a conversation are unique. After a conversation part has been accepted with a particular SequenceCode, that value can’t be repeated in the conversation. This error results in the conversation being in an error state.

Set Options.SequenceCodes in all conversation parts to sequential values. The first conversation part must have a SequenceCode value of 1, and the last part must equal the value of CallsInConversation. Resubmit the entire conversation with a new ConversationID.
215Conversation is closed and cannot accept more partsConversations are closed and ready for processing when all parts have been received. After a conversation is closed, no new parts are accepted.

When you receive this error, you don’t need to do anything unless you intended for the rejected conversation part to be part of the closed conversation.
218Too many objectsLimit the number of API objects in each request. For more information, see API Limits and Guidelines.
226A request may not have ScheduledTime greater than 30 days from nowSchedule conversation and non-conversation messages 30 days in the future or fewer.
227An unsecure response address specified in the 'SendResponseTo' parameter.Use an HTTPS endpoint for HTTP callbacks. You can’t send callbacks from the Async API to unsecured HTTP endpoints.