Status Codes

SDK status codes

-4

The application has not called `connect()`. Call `connect()` and wait for a successful connection before invoking SDK methods.

Call NCEngine.connect() and wait for the connection success callback before calling other SDK methods.

-3

The cancel or pause operation failed because the target media transfer was not found.

Verify the message ID or transfer handle before calling cancel/pause.

-1

An unknown error occurred.

If this error persists, contact support with your App Key, user ID, and the time the error occurred so that server-side logs can be retrieved.

0

The operation completed successfully.

405

The message was not delivered because the recipient has added you to their blocklist.

Remove the user from the blocklist via the Server API if your use case requires it.

407

The recipient only accepts messages from users on their allowlist, and the sender is not on it.

Add the sender to the recipient's allowlist using the allowlist Server API.

1004

The request failed because of an authentication error.

Check that the token and App Key are valid and have not expired. Re-authenticate if necessary.

20109

The system channel only supports `RC:SRSMsg` messages. This message type is not allowed in a system channel.

Send only RC:SRSMsg messages to system channels. Use a different channel type for other message types.

20112

The message was rejected because the content contains sensitive words.

Remove the sensitive content and resend.

20113

The message failed content moderation review.

Review your content moderation policies in the console and adjust message content accordingly.

20114

The message can no longer be edited because the allowed modification window has passed.

Messages can only be edited within the permitted time window after sending. No action is required unless you need to adjust the time limit via the console.

20115

The message body (serialized as JSON) exceeds the maximum allowed size of 128 KB.

Reduce the message body size. For image messages, ensure the base64-encoded thumbnail does not exceed 80 KB.

20116

This message type does not support modification.

Check whether the message type supports editing before calling the modify API.

20512

The App Key's data center does not match the data center used for this request.

Ensure that the server API address, client area code, and App Key all correspond to the same data center (domestic or overseas).

20604

The sending rate limit was exceeded. A maximum of 5 messages per second is allowed.

Add a delay between consecutive sends to keep the rate below 5 messages per second.

20606

The operation is not supported. The server has disabled it (private cloud only).

Contact support to verify which operations are available for your plan.

20607

The query rate limit was exceeded. The default limit is 50 requests per second.

Rate-limit your query calls to fewer than 50 per second.

21501

The message was blocked because it contains sensitive words. The sender cannot send this message.

Check the sensitive word list in the embedded console. Remove the sensitive words or change the filter mode.

21502

The message was delivered, but sensitive words were replaced. The recipient receives the modified version.

Check the sensitive word list in the embedded console. The filter mode is set to replace. This is informational.

22201

The original message for the expansion does not exist. Community channel messages are retained for 7 days by default.

Check the message's sentTime. If it is older than 7 days, the message has been deleted. Verify using the community channel history message API.

22202

The original message does not support expansion. Expansion is only available for messages sent with `canIncludeExpansion = true`.

Set canIncludeExpansion = true when sending the message to enable expansion.

22203

The expansion content format is invalid. The expansion value must be a valid JSON string, for example `{"key":"value"}`.

Ensure the expansion content is a valid JSON string before calling the expansion API.

22204

The caller does not have permission to expand this message. Check that the channel type value is `10`.

Verify the channel type passed to the expansion API.

22406

The user is not a member of this group.

Verify group membership via the console or the group query API. Add the user to the group as needed.

22408

The user has been muted in this group.

Unmute the user via the group mute Server API if your use case requires it.

23406

The user is not a member of this open channel. Open channels have an auto-destroy and auto-exit mechanism for offline members.

Verify membership using the console. The user may have been removed due to the auto-exit policy. Re-join the channel as needed.

23407

The mute allowlist member count for this open channel exceeds the limit (5 at creation, 20 maximum).

Refer to the open channel mute allowlist Server API documentation.

23408

The user has been muted in this open channel.

Unmute the user using the appropriate open channel mute API (global mute, channel-wide mute, or individual user mute).

23409

The user has been kicked and banned from this open channel. The ban duration is set by the Server API call.

Use the unban open channel user Server API to lift the restriction.

23410

The open channel does not exist. It may have been destroyed automatically or not yet created.

Verify the open channel status via the console. It may have been destroyed by the auto-destroy mechanism.

23411

The open channel member count has reached the configured limit.

The default limit is unlimited. If you configured a member limit, contact support to adjust it.

23412

One or more parameters passed to the open channel API are invalid.

Check the API documentation and ensure all parameters are non-null and within valid ranges.

23414

The open channel cloud message storage service is not activated.

Contact support to enable the open channel cloud message storage service.

23423

The number of KV properties in this open channel exceeds the maximum of 100.

Remove unused KV entries before adding new ones. The default limit is 100 per channel.

23424

The caller does not have permission to overwrite an existing KV property owned by another user.

Use the force-set API if your use case requires overwriting another user's KV entry.

23425

The open channel KV API call rate exceeded the limit. A single open channel can set or delete KV properties at most 100 times per second.

Throttle KV set/delete operations and retry after a short delay.

23426

The open channel custom KV property service is not enabled.

Enable the open channel KV service in the console under IM Service → Feature Settings.

23427

The specified KV property key does not exist.

Contact support if this error is unexpected.

23428

A batch KV set or delete operation partially failed.

Contact support and provide the operation details.

23429

The batch KV operation count exceeds the limit of 10 items per call.

Split the operation into batches of 10 or fewer.

23431

Setting the open channel KV property failed because another client modified the same key concurrently.

Wait briefly and retry to avoid simultaneous updates to the same KV entry from multiple clients.

23437

The extra information passed when joining an open channel exceeds the maximum length (128 characters by default).

Reduce the length of the extra information. The limit can be changed via the server configuration.

24360

The client is not allowed to set this profile property. The `uniqueId` field can only be set via the Server API.

Remove uniqueId from the updateMyUserProfile call. Use the Server API to set uniqueId if needed.

24361

The specified key is not in the list of supported basic profile properties.

Refer to the user profile Server API documentation for valid property keys.

24362

The specified key is not in the configured extended profile properties.

Add the key in the console under IM Service → Information Hosting → Custom User Properties.

24363

The number of extended profile properties exceeds the maximum of 20.

Remove unused extended properties before adding new ones.

24364

A profile property value exceeds the maximum length of 256 characters.

Shorten the value to 256 characters or fewer.

24365

The batch user profile query count exceeds the allowed limit (20 per client call, 100 per Server API call).

Split the query into smaller batches.

24366

The user does not exist in the hosted user profile service.

Register the user first via the user profile Server API, then retry.

24367

This profile property only accepts numeric values. Fields such as gender, role, and level must be integers.

Pass an integer value for this property.

24368

The profile property value exceeds the configured allowed range.

Check the configured range for this property in the console and adjust the value.

24369

The user profile hosting service is not enabled.

User profile hosting is enabled by default. Contact support if you receive this error.

24401

The community channel feature is not activated. It is available on the premium plan and is enabled by default.

Contact support if the feature is not available on your account.

24402

The community channel service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

24403

One or more parameters passed to the community channel API are invalid.

Check the API documentation and verify that all parameter formats are correct.

24404

An unknown exception occurred in the community channel service.

Contact support with your App Key and the time the error occurred.

24406

The current user is not a member of this community channel.

Verify membership via the console or the community channel Server API.

24408

The user has been muted in this community channel.

Refer to the community channel mute service documentation to unmute the user.

24410

The specified community channel does not exist.

Create the community channel via the console before performing operations on it.

24411

The community channel member count has exceeded the allowed maximum.

Contact support to adjust the member limit if needed.

24412

The user has reached the maximum number of community channels they can join (100).

The user must leave an existing community channel before joining a new one.

24413

The number of channels in this community group exceeds the limit of 50.

Delete unused channels before creating new ones.

24414

The specified community channel ID does not exist.

Create the channel first via the console or the Server API.

24415

The message sending rate in this community channel exceeds the default limit. By default, each channel is limited to 30 messages per second.

Introduce a delay between sends or implement retry logic to stay within the per-channel rate limit.

24416

The user is not a member of this private community channel.

Add the user to the private channel via the Server API.

25101

The recall message request contains invalid parameters.

Verify all parameters match the recall API specification.

25102

The cloud message storage service for direct and group channels is not activated.

Contact support to enable the cloud message storage service.

25104

An unknown exception occurred on the server.

Contact support with your App Key and the time the error occurred.

25107

The server is configured to allow users to recall only their own messages. Attempting to recall another user's message returned this error.

Only recall messages sent by the current user. Contact support if you need to change the recall permission setting.

25402

The hosting service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

25403

The hosting service received invalid parameters.

Check the request parameters against the hosting service API documentation.

25404

The operation is not allowed. Only the group owner can modify group permission settings.

Verify the group owner ID using the batch group profile query API.

25405

The caller does not have permission to perform this operation.

Check the group's permissions field using the batch group profile query API.

25406

One or more parameter values exceed the allowed length.

Check the API documentation for parameter length limits and trim values accordingly.

25407

A parameter contains invalid or illegal characters.

The built-in group property key does not exist. Check the key name against the supported list.

25408

The parameter value must be a number.

Pass a numeric value for this parameter.

25409

The specified group ID already exists. No need to create it again.

Use the existing group directly, or choose a different group ID.

25410

The specified group ID does not exist.

Create the group first, or verify the group ID.

25411

The operation would exceed the group member limit. A single invite can add at most 30 users, and the total group size cannot exceed 3,000.

Invite users in smaller batches, or contact support to adjust the member limit.

25412

The specified member is already in the group. No further action is required.

Skip users who are already members when processing bulk invite or join operations.

25413

This property cannot be modified by the client. It can only be modified via the Server API.

Check which properties allow client-side modification in the console under Information Hosting → Group Custom Attributes.

25414

The group is configured to reject all join requests.

Check the group's permissions.joinPermission setting using the batch group profile query API.

25415

The specified extended information key does not exist in the group's custom attributes.

Add the key in the console under Information Hosting → Group Custom Attributes.

25416

The query rate for group hosting exceeded the limit (5 requests per second, web only by default).

Reduce the query frequency to stay within the rate limit.

25417

The group owner cannot be kicked or removed from the group.

Transfer ownership to another member first, then remove the previous owner if needed.

25418

The specified user is not in the group.

Verify group membership using the get specific group member API.

25419

The admin or follower count has exceeded the limit. Maximum admins: 20. Maximum followers: 200. Maximum members: 3,000.

Remove existing admins or followers before adding new ones.

25420

The specified user is not an admin in this group.

Assign the admin role to the user using the set group admin API.

25421

No matching invitation or join application was found. Applications and invitations expire after 7 days.

Check whether the invitation was sent and whether it is still within the 7-day validity period. Resend if expired.

25422

The query count exceeds the limit (20 groups per query, 100 members per member query).

Split the query into smaller batches.

25423

The group name cannot be empty.

Provide a non-empty group name when creating or updating a group.

25424

Joining this group requires admin approval.

The join request has been submitted. Wait for an admin to approve it.

25425

The group owner cannot be assigned the admin role.

Use the get specific group member API to verify a user's current role before setting them as admin.

25426

The caller does not have permission to invite users to this group.

Check the group's invitePermission setting and the caller's role in the group.

25427

The group is configured to require invitees to accept before joining.

Check the group's inviteHandlePermission setting in the group profile.

25428

The join request or invitation was already handled by another admin before this action was taken.

Handle this gracefully in the UI (for example, show a "already processed" message).

25429

Legacy groups that were not imported into the hosted service cannot use hosting APIs.

Import the group data using the group hosting import API.

25430

The group ID is invalid because it contains special characters. Only letters and digits are allowed.

Use only alphanumeric characters in group IDs.

25432

The page token could not be parsed. It may be malformed or not from the latest response.

Use the pageToken value returned directly from the last paginated API response.

25460

The users are already mutual friends. The operation is not needed.

Check the friend relationship before sending a friend request.

25461

The target user requires approval before adding them as a friend.

The friend request has been submitted. Wait for the target user's response.

25462

The target user has added the current user to their blocklist. A friend request cannot be sent.

The target user must remove the current user from their blocklist before a friend request can be made.

25463

The target user has enabled an allowlist and the current user is not on it.

The target user must add the current user to their allowlist first.

25464

The target user is on the current user's blocklist.

Remove the target user from the blocklist before sending a friend request.

25465

The current user has enabled an allowlist and the target user is not on it.

Add the target user to the current user's allowlist first.

25466

The friend request does not exist or has expired. Friend requests expire after 7 days.

Verify the user ID and check whether the request is still within the 7-day validity window.

25467

The current user has reached the maximum friend count of 3,000.

The user must remove existing friends before adding new ones.

25468

The target user has reached the maximum friend count of 3,000.

The target user must remove existing friends before new friend requests can be accepted.

25469

The users are not friends. This operation requires a mutual friend relationship.

Verify the friend relationship before calling this API.

25470

The friend custom property count exceeds the maximum of 10.

Remove unused custom properties before adding new ones.

25471

The target user has disabled incoming friend requests.

Check the target user's friend add permission level using the query API.

25472

The specified user does not exist.

Register the user first using the user registration Server API.

25473

A user cannot add themselves as a friend.

Ensure that the sender's user ID and the target user ID are different.

25474

Robot users cannot be added as friends.

Only non-robot users can be added as friends.

25480

The user profile update failed content review.

Check your content moderation policies and revise the profile content accordingly.

26001

The push setting request contains invalid parameters.

Contact support with details about the API call.

26002

The client version is too old to sync. The user-level settings feature may not be enabled.

Submit a ticket to enable user-level settings. If already enabled, contact support.

26003

An internal service error occurred.

Contact support with your App Key and the time the error occurred.

26004

The number of tags exceeds the maximum of 20.

Remove unused tags before adding new ones.

26005

Read receipt V4 is not activated on this account.

Contact support to enable read receipt V4.

26006

The server-driven unread count feature is not activated.

Contact support to confirm whether the server-driven unread count feature is enabled for your account.

26007

The message ID order is incorrect. `startMsgId` must be earlier in time than `endMsgId`.

Ensure startMsgId corresponds to a timestamp that is earlier than endMsgId.

26008

The reported timestamp does not support synchronization.

Verify the API usage and timestamp semantics. Retry with the timestamp value expected by the sync API.

26009

The specified message ID is invalid.

Verify the message UID parameter being passed to the API.

26010

One or more request parameters are incorrect.

Contact support with the API name, parameters, and the time the error occurred.

26020

The online presence subscription feature is not enabled.

Contact support to enable the client online status subscription feature.

26021

The user has reached the maximum number of subscribers (5,000).

No further subscribers can be added until the count drops below the limit.

26022

The user has subscribed to the maximum number of users (5,000).

Unsubscribe from users that are no longer needed before subscribing to new ones.

26101

The short video service is not activated.

Enable the short video service via the console.

26106

The file size exceeds the maximum upload limit of 100 MB.

Compress or reduce the file size before uploading.

26107

The `size` parameter is required when file size limiting is enabled.

Pass the file size in bytes when uploading.

26200

The translation succeeded.

26201

Translation failed due to an internal authentication failure or expired token.

Re-authenticate to obtain a new token and retry the translation request.

26202

Translation failed because the translation provider rejected the authentication token.

Refresh the authentication token and retry.

26203

The translation provider returned a failure response.

Contact support and provide the provider error details if available.

26204

The translation feature is not enabled.

Contact support to enable the translation service.

26206

The server-side authentication token secret is not configured. Enable it in the console.

Enable the AI Text Translation feature in the console.

26208

The speech-to-text extraction result is empty. Check the audio codec type.

Contact support with the audio message details.

26209

The language setting is invalid.

Contact support with the language code being used.

26210

The audio encoding format setting is invalid.

Contact support with the encoding format details.

26314

Read receipt V5 is not activated.

Contact support to enable read receipt V5.

26315

The requested read receipt method is not supported.

Check the V5 read receipt API documentation for supported methods.

26316

A parameter length exceeds the allowed limit for read receipt V5.

Reduce the parameter length to the allowed maximum.

26317

The specified channel type is not supported by read receipt V5.

Use a supported channel type for V5 read receipts.

26318

The specified query type is not supported by read receipt V5.

Use a supported query type as defined in the V5 documentation.

26320

The current user is not the sender of the message. Only the sender can perform this operation.

Ensure the current user is the original sender of the message.

26321

This message does not require a read receipt.

Skip the read receipt request for messages that don't require it.

26322

The message referenced in the read receipt request does not exist.

Verify the message UID before sending a read receipt.

28300

The voice-to-text service is not enabled.

Enable the voice-to-text service via the console or contact support.

28304

The voice-to-text conversion failed.

Verify the audio format and content, then retry.

28305

The voice-to-text service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

28306

A required parameter for the voice-to-text request is missing.

Check the API documentation and provide all required parameters.

28307

The voice-to-text usage limit has been exceeded.

Contact support to increase your usage quota.

28400

The translation V2 service is not activated.

Contact support to enable translation V2.

28401

The translation V2 request failed.

Retry the request. If the issue persists, contact support.

28402

The translation V2 service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

28403

Required parameters are missing from the translation V2 request.

Check the API documentation and provide all required parameters.

28404

One or more translation V2 parameters have an invalid format.

Verify the parameter formats against the API documentation.

28405

The translation V2 usage quota has been exceeded.

Contact support to increase the quota.

28406

The text submitted for translation exceeds the maximum allowed length.

Split the text into shorter segments and translate them separately.

28407

The specified language is not supported by the translation V2 service.

Use a supported language code. Refer to the translation documentation for the list of supported languages.

29002

The specified stream does not exist.

Verify the stream identifier and ensure the stream was created before reading it.

29003

The streaming session timed out because no data was received for 30 seconds.

Ensure the data source sends chunks at least once every 30 seconds.

29004

The streaming session exceeded the 30-minute total time limit.

Split long streaming sessions into multiple streams within the 30-minute limit.

29005

The streaming message content failed review and the data has been deleted.

Review content moderation policies and ensure streaming content complies with them.

29006

The stream data exceeded 128 KB and was truncated.

Reduce the size of each stream chunk to stay under 128 KB.

29007

The streaming message service encountered an internal exception.

Contact support with your App Key and the time the error occurred.

29301

The LLM service request failed.

Retry the request. If the issue persists, contact support.

29302

The LLM service returned an error response.

Check the response details and contact support if the issue persists.

29303

The LLM service did not respond within the timeout period.

Retry the request. If timeouts persist, contact support.

29310

The specified agent ID was not found.

Verify the agent ID and ensure the agent has been created and configured.

29311

The specified LLM provider is not supported.

Use a supported LLM provider. Contact support for the list of available providers.

29320

The LLM/agent service request parameter format is invalid.

Verify the parameter formats against the agent API documentation.

29321

The `channelType` parameter is invalid in the LLM/agent service request.

Check the supported channelType values in the agent API documentation.

29322

The `channelId` parameter is invalid in the LLM/agent service request.

Provide a valid, non-empty channel ID.

29323

The `targetId` parameter is invalid in the LLM/agent service request.

Provide a valid target ID.

29324

The `message.userId` field is invalid in the LLM/agent service request.

Provide a valid message sender user ID in the request payload.

29325

The `message.messageId` field is invalid in the LLM/agent service request.

Provide a valid message ID in the request payload.

29326

The `message.username` field is invalid in the LLM/agent service request.

Provide a valid username string in the request payload.

29327

The `message.type` field is invalid in the LLM/agent service request.

Provide a valid message type identifier supported by the service.

29328

The `message.content` field is invalid in the LLM/agent service request.

Provide a valid message content payload.

29329

The `message.timestamp` field is invalid in the LLM/agent service request.

Provide a valid message timestamp in the expected format.

29330

The `agentId` parameter is invalid in the LLM/agent service request.

Provide a valid agent ID.

29331

The number of keys in `customInfo` exceeds the allowed limit in the LLM/agent service request.

Reduce the number of customInfo keys to stay within the service limit.

29332

One or more `customInfo` key or value lengths exceed the allowed limit in the LLM/agent service request.

Shorten the customInfo keys or values to stay within the service limit.

29399

An unknown error occurred in the LLM/agent service.

Contact support with your App Key and the time the error occurred.

30001

The current connection has been released.

Monitor connection state using the connection status handler. Retry or switch to a more stable network.

30002

The connection is not available. Other async APIs require a successful connection before they can be called.

Call NCEngine.connect() first and wait for the success callback before calling other APIs.

30003

The server did not acknowledge the client's message request within the timeout period.

Retry the operation after a short delay. If the issue persists, contact support with your App Key, user ID, and the time the error occurred.

30004

The HTTP request failed during navigation.

Retry after a delay or switch to a more stable network.

30005

The navigation server address request timed out.

Retry after a delay or switch to a more stable network.

30006

Receiving the HTTP response failed during navigation.

Retry after a delay or switch to a more stable network.

30007

The navigation returned an abnormal result.

Retry after a delay. If the issue persists, contact support.

30008

The navigation HTTP response contains a data format error.

Retry after a delay. If the issue persists, contact support.

30009

No valid IP address was found in the navigation response.

Contact support with your App Key, user ID, and the time the error occurred.

30010

Failed to create a connection after trying all CMP server addresses.

Retry after a delay or switch to a more stable network.

30011

The connection was disconnected.

Retry after a delay or switch to a more stable network.

30012

The PING to the server failed. This is typically caused by a network issue.

The SDK automatically attempts to reconnect. No manual action is required.

30013

The PING timed out. This is typically caused by a network issue.

The SDK automatically attempts to reconnect. No manual action is required.

30014

Sending the signaling message failed. This can occur due to network issues or a failed media upload.

Check the network connection. For media messages, verify that the upload succeeded and that the remote URL is not empty.

30015

The connection attempt was rejected because connections are being made too frequently.

Add a delay between connection attempts.

30016

The message body (serialized as JSON) exceeds 128 KB. A common cause is an oversized thumbnail in an image message.

For image messages, keep the base64-encoded thumbnail under 80 KB. Ensure the total MessageContent does not exceed 128 KB.

30017

This message type does not support sending.

Check that the message type is a sendable type as defined in the SDK documentation.

30019

The network is down or unreachable.

Retry after restoring network connectivity.

30021

The TCP connection succeeded but the RMTP handshake failed.

Retry after a delay. If the issue persists, contact support.

31000

The connection acknowledgement timed out.

Contact support with your App Key, user ID, and the time the error occurred.

31001

The signaling protocol version is mismatched.

Contact support with your App Key and SDK version.

31002

The client info field format is incorrect. The expected format is `{platform}-{deviceInfo}-{sdkVersion}`.

Contact support with your App Key and the SDK version in use.

31003

The connection service is not activated. This may occur with mini-program or desktop client configurations.

Contact support with your App Key and user ID to verify service activation.

31004

The token is invalid, the App Key and token do not match, or the token has expired.

Verify that the App Key used during initialization matches the one used to generate the token. If using an overseas data center, confirm the correct area code is set. Check the token expiry in the console under Basic Info.

31005

App verification failed. The app certificate verification feature is enabled but the check did not pass.

Contact support with your App Key and package name.

31006

The connection was redirected. The SDK handles this automatically.

No action needed. If this error causes issues, contact support.

31007

The application package name does not match the value registered in the console.

Contact support with your App Key and the package name being used.

31008

The App Key has been suspended or deleted.

Restore the App Key in the console under App Management.

31009

Connection failed because the user is banned.

Unban the user via the Server API as needed.

31010

The user was kicked offline. By default, the same account can be active on one device per platform type simultaneously.

If multi-device login is required for the same platform type, configure the multi-device simultaneous login setting.

31011

The IM connection was passively disconnected because the user was banned.

Unban the user via the Server API as needed.

31012

The connection link encryption authentication failed.

Contact support with your App Key and package name.

31020

The token has expired.

Check the token expiry setting in the console under Basic Info. Request a new token and reconnect.

31023

A device of the same type is already online. This error is returned when the "do not kick online clients" option is enabled.

Refer to the reconnection and multi-device kick documentation.

31024

The total connection count exceeds the configured concurrency limit (private cloud only).

The limit is set per App Key. Contact your private cloud administrator to adjust it.

31025

The client is connecting to the wrong environment (for example, using a development App Key against the production environment).

Ensure the App Key matches the target environment (development vs. production).

31026

App server co-authentication is enabled and the authentication with the app server failed.

Contact support with your App Key and package name.

31027

This one-time token has already been used. A one-time token can only establish a connection once.

Request a new token from the app server and use it to reconnect.

31029

The user account has been deactivated.

Check whether the user is in the deactivated user list. Reactivate the user ID via the Server API if needed.

31030

The private cloud license check failed or the App License has expired.

Check the identifier and license expiry in the private cloud management console. Contact your account manager if they have expired.

31031

The `channelType` parameter is invalid in the agent API request.

Provide a valid channel type supported by the agent service.

31032

The `customInfo` prompt type or payload is invalid in the agent API request.

Verify the customInfo structure and use a supported prompt type.

31033

The agent service is unavailable.

Retry later. If the issue persists, contact support.

31034

The `message.userId` field is invalid in the agent API request.

Provide a valid message sender user ID.

31035

The `message.messageId` field is invalid in the agent API request.

Provide a valid message ID.

31036

The `message.username` field is invalid in the agent API request.

Provide a valid username string.

31037

The `message.type` field is invalid in the agent API request.

Provide a valid message type supported by the agent service.

31038

The `message.content` field is invalid in the agent API request.

Provide a valid message content payload.

31039

The `message.timestamp` field is invalid in the agent API request.

Provide a valid message timestamp.

31040

The `agentId` parameter is invalid in the agent API request.

Provide a valid agent ID.

31041

The `recommendationParams` parameter type is invalid in the agent API request.

Verify the structure and type of recommendationParams.

31042

The context message list is invalid in the agent API request.

Provide a valid context message list with the expected item structure.

31043

A context message item is invalid in the agent API request.

Validate each context message object before sending the request.

31044

The number of context messages in the agent API request exceeds the maximum allowed.

Reduce the number of context messages in the request.

32001

An internal protocol layer error occurred during a query, upload, or download operation.

Contact support with your App Key, user ID, and the time the error occurred.

32002

A protocol layer internal error occurred.

Contact support with your App Key, user ID, and the time the error occurred.

32011

The server actively closed the connection (QUIC protocol only).

Contact support with your App Key, user ID, and the time the error occurred.

32054

The connection was reset by the server, possibly because the carrier flagged it as invalid. The SDK automatically triggers a reconnection.

No manual action is required. If this error occurs frequently, contact support with network environment details.

32061

The connection was refused by the server.

Retry after a delay. If the issue persists, contact support.

33000

The message could not be saved to the local database when sending or inserting.

Check that the device has sufficient storage and that connect() completed successfully.

33001

The SDK protocol stack is not initialized. Either `init()` was not called, or a required native library failed to load.

Ensure NCEngine.init() is called before any other SDK method.

33002

A database error occurred.

Ensure init() and connect() have completed successfully. Contact support if the issue persists.

33003

The input parameters for the API call are invalid.

Check the API documentation and verify that all parameters meet the documented requirements.

33004

The communication channel is invalid.

Contact support with your App Key, user ID, and the time the error occurred.

33006

A connection is already in progress. The new `connect()` call was rejected.

Wait for the current connection attempt to complete before calling connect() again.

33007

The cloud message storage service for direct and group channels is not activated.

Contact support to enable the cloud message storage service.

33008

Inserting the message into the local database failed.

Ensure init() and connect() have completed. Check device storage availability.

33009

The open channel was reclaimed by the server.

Verify the open channel status in the console.

33010

The database encryption migration failed, typically because of insufficient disk space.

Free up storage space. The migration usually succeeds automatically on the next connection attempt.

33011

The database decryption migration failed, typically because of insufficient disk space.

Free up storage space. The migration usually succeeds automatically on the next connection attempt.

33012

The database file could not be deleted, possibly because it is still in use by an active connection.

Disconnect before attempting to remove the database file.

33100

The specified tag does not exist.

Use the get tags API to confirm whether the tag exists, then create it if needed.

33101

A tag with this ID already exists.

Use the existing tag, or use a different tag ID.

33102

The tag is not associated with the specified channel.

Use the get tags for channel API to confirm which tags are associated.

33103

The method is currently executing and cannot be called again until it completes.

Wait for the current operation to finish before calling the method again.

33401

The message has not been sent successfully yet and cannot be edited.

Wait for the message to be delivered successfully before attempting to edit it.

33402

The message modification time limit has been exceeded.

Messages can only be edited within the configured time window after sending.

34001

A connection already exists. There is no need to call `connect()` again.

Skip the connect() call if the SDK is already connected.

34002

The short video duration exceeds the maximum of 2 minutes.

Trim the video to 2 minutes or less before sending.

34003

The GIF file size exceeds the maximum of 2 MB.

Reduce the GIF file size to 2 MB or less.

34004

The open channel KV state has not finished syncing. Querying KV immediately after joining a channel may return unsynced data.

Wait a short time after joining the channel before querying KV entries, or wait for the onMetadataSynced callback.

34005

The connection environment is incorrect (private cloud only). For example, using a public cloud SDK against a private cloud deployment.

Use the correct SDK build for your deployment environment (public cloud vs. private cloud).

34006

The connection timed out.

Monitor connection state and retry. Ensure the network is stable.

34007

The queried public service profile does not exist. Verify the service type and service ID match.

Confirm both the service type and service ID are correct.

34008

The message cannot be expanded. Expansion is only supported for direct, group, and community channels. The message must have `canIncludeExpansion` set to `true` when sent.

Set canIncludeExpansion = true on the message before sending.

34009

Message expansion failed, typically due to a network issue.

Verify that the SDK is connected and retry.

34010

The message expansion data exceeds the limit. Default limits: key ≤ 32 characters, value ≤ 4,096 characters, total key-value pairs ≤ 300.

Reduce the size of the expansion data to stay within the limits.

34011

The media file HTTP upload failed.

Retry after a delay or switch to a more stable network.

34012

The specified channel type does not support tags. Tags are only supported for direct, group, and system channels.

Use a supported channel type when adding tags.

34013

The number of channels to add or remove in a tag operation exceeds the maximum of 1,000.

Split the operation into batches of 1,000 or fewer.

34014

The group read receipt version is not supported. Verify the API matches the integrated SDK.

Check which read receipt version your SDK and service plan support.

34015

Video compression failed. The video resource may be inaccessible or invalid.

Verify the video file path and permissions before attempting to compress.

34016

The user-level settings feature is not enabled.

Contact support to enable user-level settings.

34017

The message interceptor returned a null message.

Review the MessageInterceptor implementation and ensure it never returns null.

34018

The media file upload failed because the file does not exist or has a size of 0.

Verify that the media file exists, is accessible, and has a non-zero size.

34019

The media file format is not supported for upload.

Contact support with your App Key and the file format you are trying to upload.

34020

The file has expired or been cleaned up. Short videos are stored for 7 days; other files are stored for 6 months.

Check the message's sentTime to determine whether the file has passed its retention period.

34021

The message type has not been registered. Custom messages must be registered before use.

Register custom message types using the message registration API. For built-in messages, ensure init() completed successfully.

34022

The called API does not support the community channel type.

Verify that the channel type is not ULTRAGROUP when calling APIs that don't support it.

34023

The `readReceiptUsersOption` parameter is null or invalid.

Provide a valid non-null read receipt users query option object.

34024

The specified community channel ID does not exist.

Verify the community channel ID before calling the API.

34025

The expansion failed because the message's channel type does not match the API's supported types.

For direct and group channels, use the standard expansion API. For community channels, use the UltraGroup-specific expansion API.

34026

The HTTP request threw an IO exception. The device may not have an active network connection.

Retry after restoring network connectivity.

34027

The HTTP request timed out.

Retry after a delay or switch to a more stable network.

34028

The request does not allow redirects. Use the real file URL instead of a redirecting URL.

Replace the URL with the final non-redirecting file address.

34029

This message does not support read receipts.

Only enable read receipt sending for supported message types and channel scenarios.

34030

The media file download was rejected with a 403 error.

Check download permissions for the media resource.

34100

The `authToken` is not set or is empty.

Provide a non-empty jwtToken when calling the translation API.

34101

The text to translate is empty.

Provide a non-empty text input for translation.

34102

The target language is empty.

Specify a valid target language code.

34103

The source language is empty.

Specify a valid source language code or leave it as auto-detect if supported.

34104

The translation server URL is empty. The translation service may not be enabled.

Confirm the translation service is enabled for your App Key. Reinstall and retry if it was recently activated.

34105

The App Key passed to the translation API is empty.

Ensure NCEngine.init() is called with a valid App Key before using the translation API.

34106

The server returned invalid data for the translation request.

Contact support with your App Key, user ID, and the time the error occurred.

34129

The `ConnectOption` parameter passed to `connect()` is null.

Provide a non-null ConnectOption when calling NCEngine.connect().

34131

The SDK version number parameter is invalid. It must have at least 3 segments and consist of integers.

Use the SDK version string provided by the SDK itself. Do not construct version strings manually.

34200

The language code passed to the API is invalid or empty.

Provide a valid, non-empty language code.

34201

The specified channel type is not supported by the called API.

Check the supported channel types for this API in the documentation.

34202

The timestamp parameter is invalid (for example, less than or equal to 0).

Provide a valid positive timestamp in milliseconds.

34203

The message UID is invalid or empty.

Ensure the message UID is a non-empty string.

34204

The message ID is invalid (must be greater than 0), or no message with this ID was found.

Verify the message ID is positive and refers to an existing message in the database.

34205

The `Message` object or `MessageContent` is null or of an incorrect type.

Ensure the message object and its content are non-null and of the correct type.

34206

The message list is null, empty, or contains invalid entries.

Provide a non-empty list. For batch operations, ensure the count does not exceed the documented limit.

34207

The `mediaType` parameter is null.

Provide a valid non-null MediaType value.

34208

The `requestUrl` (media URL) parameter is invalid or empty.

Provide a valid, non-empty URL.

34209

The `ConversationType` parameter is null.

Provide a valid, non-null ConversationType value.

34210

The `targetId` is null or empty, or its length is not within the valid range of 1–64 characters.

Provide a non-empty targetId with a length between 1 and 64 characters.

34211

The `channelId` is null for an API that expects an empty string, or its length exceeds 20 characters.

Pass an empty string "" instead of null where a channel ID is not applicable.

34212

The tag ID is null, not a string, or its length is not within the valid range of 1–10 characters.

Provide a non-null string tag ID with a length between 1 and 10 characters.

34213

The tag name is null, not a string, or its length is not within the valid range of 1–15 characters.

Provide a non-null string tag name with a length between 1 and 15 characters.

34214

The `userId` is null or empty, or its length exceeds 64 characters.

Provide a non-null, non-empty userId with a maximum length of 64 characters.

34215

The `userIdList` is null, empty, or contains invalid user IDs.

Provide a non-empty list where each userId is a non-null string with a maximum length of 64 characters.

34218

The offline message duration is outside the valid range of 1–7 days.

Pass a value between 1 and 7 inclusive.

34219

The `count` field in `HistoryMessageOption` is not a positive integer.

Set count to a positive integer value.

34220

The message expansion map is invalid. Keys must be alphanumeric with `+ = - _`, and values must be strings.

Ensure the expansion map is a non-empty HashMap<String, String> where keys use only alphanumeric characters and + = - _.

34221

The expansion key array passed to `removeUltraGroupMessageExpansion` is null or empty.

Provide a non-null, non-empty ArrayList<String> of keys to remove.

34223

The `Message.content` passed to `sendMediaMessage` is not a media message type.

Use sendMessage() for regular messages and sendMediaMessage() only for messages whose content extends MediaMessageContent.

34224

The time string parameter is null or empty.

Provide a non-empty string value for the time parameter.

34225

The `ConversationIdentifier` parameter is null.

Provide a non-null ConversationIdentifier object.

34228

The `PushNotificationLevel` is null or set to `NONE`.

Provide a valid, non-null PushNotificationLevel value other than NONE.

34229

The `messageIds` array is null or has a length of 0.

Provide a non-null array with at least one message ID.

34230

The `ReceivedStatus` parameter is null.

Provide a valid non-null ReceivedStatus value.

34231

The community channel type (`channelType`) is null or invalid.

Provide a valid non-null channel type.

34232

The `count` parameter is invalid. Check the API documentation for its valid range.

Provide a count value within the range specified in the API documentation.

34233

The `sendTime` parameter is less than 0.

Provide a sendTime value greater than or equal to 0.

34234

The local file path does not exist.

Verify the file path is accessible before passing it to the API.

34235

The `mediaUrl` is empty.

Provide a non-empty mediaUrl.

34236

The `uniqueId` is null or an empty string.

Provide a non-null, non-empty uniqueId.

34237

The `MessageTag` or its `value()` is null or empty.

Ensure the MessageTag and its value are non-null and non-empty.

34238

The proxy configuration is invalid. The `RongIMProxy` object is null, or the host is empty, or the port is not positive.

Provide a valid RongIMProxy with a non-empty host and a positive port number.

34239

The proxy test service host is invalid or empty.

Provide a non-empty, valid testHost string with a length greater than 0.

34240

The proxy test could not establish a connection to the test host.

Verify the test host address is correct and reachable from the device's network.

34241

The `recallUltraGroupMessage` API received an unsupported message type (`RecallNotificationMessage` cannot be recalled).

Only recall original user messages, not recall notification messages.

34242

The `conversations` parameter is null or contains null entries.

Provide a non-null list with no null entries.

34243

The `message` parameter is null.

Provide a non-null Message object.

34244

The `SentStatus` parameter is null or set to `SENDING`.

Provide a valid non-null SentStatus that is not SENDING.

34245

The configured proxy address is not reachable.

Verify the proxy configuration and test connectivity before applying it.

34246

Failed to update the message read receipt status.

Contact support with your App Key, user ID, and the time the error occurred.

34247

Failed to clear the message unread status.

Verify the parameters are correct, then contact support if the issue persists.

34248

Failed to set the message read time.

Verify the parameters are correct, then contact support if the issue persists.

34249

Failed to get the remote push language setting.

Retry the query. If the issue persists, contact support with the API details.

34250

Failed to get the offline message duration setting.

Retry the query. If the issue persists, contact support with the API details.

34251

Saving the file failed. The parent directory may not exist, or the device may have insufficient storage.

Check available storage and verify the destination directory exists before saving.

34252

The target file does not exist.

Verify the file path and ensure the file exists before starting the operation.

34253

The file size is invalid.

Ensure the file size is greater than 0 and matches the actual file content before uploading or downloading.

34254

The download URL is invalid.

Provide a valid downloadable URL.

34255

The file slice index is invalid.

Verify the slice index values used in the resumable transfer request.

34256

The upload ID is invalid.

Restart the upload flow and use the latest valid upload ID returned by the server.

34257

The App Key is invalid.

Ensure NCEngine.init() is called with a valid App Key before connecting.

34258

The `JoinMode` parameter is null.

Provide a valid non-null JoinMode value.

34259

The `rtcRoomId` parameter is null or not a string.

Provide a valid non-null string rtcRoomId when calling the open channel RTC binding API.

34260

The KV `key` parameter is invalid. Keys must be 1–128 characters long and match `[A-Za-z0-9+_=-]+`.

Use only alphanumeric characters and the symbols + = - _ in KV keys.

34261

The `keys` collection is null or empty.

Provide a non-null, non-empty collection of keys.

34262

The KV `value` is null or empty, or it exceeds 4 KB.

Provide a non-null, non-empty value that does not exceed 4 KB.

34263

The `entries` map is null or empty.

Provide a non-null, non-empty map.

34264

The `notificationExtra` is null or exceeds 2 KB.

Provide a non-null notificationExtra with a maximum length of 2 KB.

34265

The `ChatRoomMemberOrder` parameter is null.

Provide a valid non-null ChatRoomMemberOrder value.

34266

The `TimestampOrder` parameter is null.

Provide a valid non-null TimestampOrder value.

34267

The `MessageDirection` parameter is null.

Provide a valid non-null MessageDirection value.

34268

The `status` parameter for sending the ultra group typing indicator is null.

Provide a valid non-null status value.

34269

The `title` parameter is null or empty.

Provide a non-null, non-empty title string.

34270

The `portrait` (avatar URL) parameter is null or empty.

Provide a valid non-null, non-empty portrait URL.

34271

The `objectName` (message type identifier) is null or empty.

Provide the correct non-empty objectName for the message type.

34272

The `before` parameter is less than 0.

Provide a before value of 0 or greater.

34273

The `after` parameter is less than 0.

Provide an after value of 0 or greater.

34274

The search `keyword` is null or empty, or its length exceeds 1,000 characters.

Provide a non-empty keyword with a maximum length of 1,000 characters.

34275

The `objectName` list is null or empty.

Provide a non-null, non-empty list of message type identifiers.

34276

The `offset` parameter is less than 0.

Provide an offset of 0 or greater.

34277

The `startTime` parameter is less than 0, or it is greater than `endTime`.

Provide a startTime that is ≥ 0 and less than endTime.

34278

The `endTime` parameter is less than 0.

Provide an endTime that is 0 or greater.

34279

The `limit` parameter is not a positive integer.

Provide a positive integer limit value.

34280

The `MessageDirection` is not `SEND`. The group message delivery list API only queries sent messages.

Filter the message list to only include messages with direction SEND before calling this API.

34281

The message `SentStatus` is invalid for the requested operation.

For direct channels, only messages with status RECEIVED or READ support delivery time queries. For group channels, use SENT, RECEIVED, or READ.

34282

The target ID list is null, empty, or exceeds the maximum of 20 entries.

Provide a non-null list with 1 to 20 target IDs.

34283

The do-not-disturb span in minutes is outside the valid range of 1–1,440 minutes.

Provide a span value between 1 and 1,440 (24 hours).

34284

The `ConversationType` list is null, empty, or exceeds the maximum of 300 entries.

Provide a non-null list of 1 to 300 channel types.

34285

The message handler is invalid. Custom messages must have a `MessageHandler` configured (such as for `ImageMessage`). Short video messages require prior registration.

Configure a MessageHandler for each custom message type. Register short video messages if needed.

34287

The `ConversationIdentifier` array is null, empty, or contains more than 20 entries or invalid objects.

Provide a non-null array of 1 to 20 valid ConversationIdentifier objects.

34288

The `ClearMessageOption` array is null, empty, or contains more than 20 entries or invalid objects.

Provide a non-null array of 1 to 20 valid ClearMessageOption objects.

34289

The `startMessageUID` is null or empty, or its length exceeds 64 characters.

Provide a non-empty startMessageUID with a maximum length of 64 characters.

34290

The `endMessageUID` is null or empty, or its length exceeds 64 characters.

Provide a non-empty endMessageUID with a maximum length of 64 characters.

34291

Read receipt V4 is not supported.

Use the supported read receipt version for your SDK and service configuration.

34292

Updating read receipt V4 data is not supported.

Avoid calling V4 update APIs in this environment. Use the supported read receipt flow instead.

34296

The channel type passed to the directed message API is not supported. Supported types are `GROUP`, `ULTRA_GROUP`, `DISCUSSION`, and `RTC_ROOM`.

Verify the channel type before calling the directed message API.

34300

The media upload/download interceptor returned a null `HttpURLConnection`.

Ensure the setHttpDownloadInterceptor implementation always returns a non-null HttpURLConnection.

34301

The database is not initialized.

Ensure NCEngine.init() is called before performing database operations.

34302

The database file is corrupted.

Contact support with your App Key, user ID, and the time the error occurred.

34303

A SQL execution error occurred in the database.

Contact support with your App Key, user ID, and the time the error occurred.

34304

The queried data was not found in the database.

Verify the query parameters and check that the data exists before querying.

34305

Parsing the network response data failed.

Contact support with your App Key, user ID, and the time the error occurred.

34306

The subscription type in the `SubscribeEventRequest` is null.

Provide a valid non-null SubscribeType in the request.

34307

The subscription duration is outside the valid range of 60 seconds to 30 days (2,592,000 seconds).

Provide an expiry value between 60 and 2,592,000 seconds.

34308

The subscriber user ID list is null, empty, or contains user IDs that exceed 64 characters.

Provide a non-empty list of user IDs, each with a maximum length of 64 characters.

34309

The page size for the subscription query is outside the valid range of 1–200.

Provide a page size between 1 and 200 inclusive.

34312

The `userProfile` parameter is null.

Provide a non-null userProfile object.

34313

The `userProfileVisibility` parameter is null.

Provide a valid non-null visibility object.

34314

The `extra` parameter is invalid.

Provide a valid extra value and ensure it matches the API's length and format requirements.

34315

The database upgrade failed.

Contact support with your App Key, user ID, and the time the error occurred.

34316

The `ChatRoomReceiveMessageConfig` parameter is null.

Provide a valid non-null ChatRoomReceiveMessageConfig object.

34317

The number of open channel message level configurations exceeds the maximum of 100.

Reduce the number of configurations to 100 or fewer.

34318

The `GroupInfo` parameter is null.

Provide a valid non-null GroupInfo object.

34319

The `groupId` is null, empty after trimming, or exceeds 64 characters.

Provide a non-empty groupId with a maximum length of 64 characters.

34320

The `groupName` is null, empty after trimming, or exceeds 64 characters.

Provide a non-empty groupName with a maximum length of 64 characters.

34321

The `groupIds` array is null, empty, or contains more than 20 entries or invalid IDs.

Provide a non-null array of 1 to 20 valid group IDs, each with a maximum length of 64 characters.

34322

The `GroupMemberRole` parameter is outside the defined enum range.

Use a valid value from the GroupMemberRole enum.

34323

The `GroupApplicationStatus` array is null or contains values outside the defined enum range.

Provide a non-null array where every entry is a valid GroupApplicationStatus value.

34324

The `GroupApplicationDirection` array is null or contains values outside the defined enum range.

Provide a non-null array where every entry is a valid GroupApplicationDirection value.

34325

The `nickname` is empty after trimming or exceeds 64 characters.

Provide a non-empty nickname with a maximum length of 64 characters.

34326

The `reason` is null, empty after trimming, or exceeds 128 characters.

Provide a non-empty reason with a maximum length of 128 characters.

34327

The `remark` is null, empty after trimming, or exceeds 64 characters.

Provide a non-empty remark with a maximum length of 64 characters.

34328

The `PagingQueryOption` parameter is null.

Provide a valid non-null PagingQueryOption object.

34329

The data is currently being synchronized from the server.

Wait for the sync to complete before querying local data.

34330

The `QueryFriendsDirectionType` parameter is outside the defined enum range.

Use a valid value from the QueryFriendsDirectionType enum.

34331

The `DirectionType` parameter is outside the defined enum range.

Use a valid value from the DirectionType enum.

34332

The `FriendApplicationType` parameter is outside the defined enum range.

Use a valid value from the FriendApplicationType enum.

34333

The `FriendApplicationStatus` parameter is outside the defined enum range.

Use a valid value from the FriendApplicationStatus enum.

34334

The `FriendAddPermission` parameter is outside the defined enum range.

Use a valid value from the FriendAddPermission enum.

34335

The `extProfile` field for friend info is invalid.

Verify the format and content of the extProfile map.

34336

The real-time conversation feature is not enabled.

Contact support to enable the real-time conversation feature.

34337

The user-triggered log upload feature is not enabled.

Contact support to enable log upload.

34338

Log uploads are being triggered too frequently. The minimum interval between uploads has not been met.

Wait for the required interval before triggering another log upload.

34339

A log upload for this time period has already been submitted.

Do not submit duplicate log uploads for the same time period.

34340

The log upload failed.

Retry the upload. If the issue persists, contact support.

34341

The `pushServer` parameter is invalid.

Provide a valid pushServer configuration.

34342

The statistics server URL is invalid.

Provide a valid statistics server URL.

34343

The `pushToken` is invalid.

Provide a valid, non-null push token.

34344

Parsing the server response data failed.

Contact support with your App Key, user ID, and the time the error occurred.

35024

The message type parameter is invalid.

Provide a valid message type as defined in the SDK documentation.

35025

The sort order parameter is invalid.

Provide a valid order value.

35054

The `disableUpdateLastMessage` parameter is invalid. In community channels, this field cannot be set to `true`.

Do not set disableUpdateLastMessage = true when sending messages to a community channel.

35055

Only the default channel in a community group supports pinning.

Apply pinning only on the default community channel.

35056

The read receipt configuration for sending is incorrect.

Review the needReceipt configuration and ensure it is valid for the channel type.

35057

The voice-to-text feature is not enabled for this voice message.

Enable voice-to-text in the console before using this feature.

35058

A voice-to-text request is already in progress for this message.

Wait for the current STT request to complete before starting a new one.

35059

The message content type is not supported by the voice-to-text service.

Only send audio messages to the voice-to-text API.

35060

The translation input type is invalid.

Verify the parameter types passed to the translation API.

35061

The translation parameter list length is invalid.

Ensure the translation request list is non-empty and within the supported length.

35062

The channel translation strategy parameter is invalid.

Use a valid TranslateStrategy value.

35063

The source and target languages are the same. Translation is not required.

Specify different source and target languages.

35064

The translation mode parameter is invalid.

Use a valid translate mode value.

35065

The translation text content is invalid or empty.

Provide valid, non-empty text for translation.

39001

The streaming message feature is not available.

Contact support to enable streaming messages for your account.

39002

The concurrent streaming message request limit of 3 has been reached.

Wait for one of the active streams to complete before starting a new one.

39003

The expansion key does not support modification or deletion for streaming messages.

Check the streaming message expansion key restrictions in the documentation.

39004

The streaming message was reset while data was being pulled.

Restart the pull request from the beginning.

39005

The streaming message pull request failed.

Retry the pull request. If the issue persists, contact support.

39006

Content is already being pulled for this stream. Duplicate requests are not allowed.

Wait for the current pull request to complete before making another.

39007

The streaming message content has already been fully synced locally. No need to pull again.

Skip the pull request if the stream is already synced.