You can query IoT Platform logs in the IoT Platform console. IoT Platform logs contain the records of communication among IoT Platform, devices, and applications. This article describes the error codes in IoT Platform logs and the corresponding troubleshooting methods.

Log types

The following figure shows the log types of upstream messages.

Upstream message logs
  1. When devices send messages to IoT Platform, the corresponding message logs are printed. The topics that are used to send messages are included in the logs.
  2. When data is processed by different business modules in IoT Platform, the logs of the business modules are printed.
  3. If messages are sent to consumers by using the data forwarding or server-side subscription feature, the logs of the corresponding feature are printed. If you use the server-side subscription feature, you can configure an AMQP or Message Service (MNS) client to receive messages.

The following figure shows the log types of downstream messages.

Downstream message logs
  1. When users call API operations to publish messages, the logs of the API operations are printed. The API operation names are included in the logs.
  2. When data is processed by different business modules in IoT Platform, the logs of the business modules are printed.
  3. If messages are sent from IoT Platform to devices, the corresponding message logs are printed. The topics that are used to send messages are included in the logs.

Query IoT Platform logs

  1. Log on to the IoT Platform console.
  2. In the left-side navigation pane, choose Maintenance > Device Log. Then, click the Cloud run log tab.
  3. Select a product, specify search conditions, and then click Search.

    The following table describes the supported search conditions.

    Notice If you specify a search condition such as DeviceName or keyword that contains one of the following special characters: , '";=()[]@&&>/:\n\t\r, the condition content is split into multiple words. In this case, the query fails. The following error message is returned: The parameter is invalid when you query logs.
    Search condition Description
    DeviceName Enter a DeviceName. You can search for the logs of a device by specifying a DeviceName.
    TraceId Enter a trace ID to search for the logs of series modules.
    Keyword Enter a keyword to search for the logs that contain the keyword.
    MessageID Enter a message ID. A message ID is a unique identifier that is generated by IoT Platform for a message.

    You can search for logs by message ID only in upstream and downstream message analysis.

    State Select a status to search for logs. Valid options:
    • All
    • Successful: The HTTP status code is 200.
    • Failed: The HTTP status code is not 200.
    Time range Select a time range.

Log fields

The following table describes the log fields.

Field Description Remarks
Time The time when a log entry is printed. None
TraceId The trace ID. You can use this ID to search for series modules. None
MessageID The message ID. This field is only available in the logs that are generated when IoT Platform sends TSL commands to devices.
DeviceName The DeviceName of the device. None
Workload Type (all) By default, logs of all business types are displayed. You can query logs of a specific business type.

The following log fields that correspond to business types are displayed when logs are stored in Log Service:

  • OTA update: OTA
  • Data parsing: ScriptParsing
  • TSL data verification: ThingModel
  • Data storage: DataStorage
  • Remote configuration: RemoteConfig
  • Topological relationships: ThingTopo
  • TSL service calls: ThingService
  • Device behavior: device
  • Device-to-cloud messages: uplink
  • Cloud-to-device messages: downlink
  • API calls: ApiService
  • Server-side subscription: ServiceSubscribe
  • Device shadow: DeviceShadow
  • Data forwarding: RuleEngine
  • Subscription to topics: subscribe
  • Unsubscription from topics: unsubscribe
  • TSL messages: ThingModelMessage
  • Device jobs: ThingJob
  • Others: Other
The first-level business identifier that identifies a business module.
Operation This field includes an operation that is performed, API operation, service method, or message topic. The field value varies based on the following operation types:
  • OTA update
    • OTAFirmwarePush: pushes notifications when a firmware update is initiated, confirmed, and completed
    • OTAFirmwareRequest: queries the information about an OTA update package
    • OTAVersionReport: submits the OTA module version of a device
    • OTAProgressReport: submits the update progress of a device
  • Data parsing
    • RawDataToProtocol: converts raw data to Alink protocol data
    • ProtocolToRawData: converts Alink protocol data to raw data
  • TSL data submission
    • check: verifies the submitted TSL data based on the TSL definition.
    • For more information about the method parameter in the message body, see TSL communication topics.
  • Device behavior management
    • online: connects a device to IoT Platform
    • offline: disconnects a device from IoT Platform
The second-level business identifier.
Content The log content may contain the following parameters:
  • TraceId: the trace ID that can be used to search for series modules
  • Message: the error message. Logs of failed operations include this field.
  • Params: the request parameters. Logs of some types include this field.
  • ResultData: the result. If operations generate results, printed logs include this field. Otherwise, printed logs do not include this field.
If the data format of a product is set to Custom, logs for TSL data parsing include the hexadecimal values of raw data that is submitted by devices.
State The HTTP status code in the response. The status code 200 indicates that a call was successful. Other status codes indicate that the call failed.

For information about API operation-related error codes, see Error codes. For information about other error codes, see the following section.

None

Device behavior-related error codes

Logs for device behaviors are generated when devices go online or offline.

Error code Definition Cause Troubleshooting
200 The device goes online or offline as expected.
  • Offline: The device ends the connection with IoT Platform.
  • Online: The device establishes a connection with IoT Platform.
View the Last Online and Current Status parameters of the device on the Device Details page of the IoT Platform console.
1910 An error occurs due to an MQTT heartbeat timeout when you disconnect the device from IoT Platform. If IoT Platform does not receive a message within the keep-alive interval, the device is disconnected from IoT Platform and must reconnect to the server. Check whether the MQTT heartbeat keep-alive time exceeds the threshold.
1911 The device goes offline because the TCP connection between the device and IoT Platform is ended.
  • If a firewall or network address translation (NAT) gateway on the device side detects an inactive TCP connection, the device ends the TCP connection.
  • The TCP connection is terminated due to the complex network environment of the Internet. If the device is reconnected to IoT Platform and the business is not affected, ignore this error code.
Change the network environment, or check the firewall and gateway settings. For example, you can disable the firewall to troubleshoot the problem.
Note If TCP disconnections frequently occur, you can use TCPDUMP to obtain packet capture files and then submit a ticket.
1913 The sub-device is disconnected. The gateway goes offline. Check why the gateway goes offline by using Log Service.
401 The device has no permissions. When you add a topological relationship and authenticate the sub-device, the signature of the sub-device fails to be verified. Verify the generated signature and submitted signature by using the signature method in the Alink protocol.

For more information about the Alink protocol, see Device registration.

427 A disconnection error occurs. The device is forced to go offline because the device certificate is used by another device.
IoT Platform identifies a device only based on the device certificate (ProductKey, DeviceName, and DeviceSecret).
  • The same device certificate is burned on multiple devices.
  • The network or power supply of the device is unstable. The device is reconnected to IoT Platform immediately after an abrupt network outage or power failure. In this case, IoT Platform identifies the reconnected device as a new device. Even if the error message is returned, the device can work properly.
Check whether the device certificate is reused on the Device Details page of the IoT Platform console.
520 An error occurs in the session between the sub-device and IoT Platform.
  • The specified session does not exist because the sub-device is not connected to IoT Platform, or the sub-device is already disconnected from IoT Platform.
  • The session exists, but the session is not established by using the current gateway.
On the Device List tab of the Devices page, search for the required device and view the device status.
521 The device has been deleted. The device has been deleted from IoT Platform. On the Device List tab of the Devices page, search for the required device to check whether the device has been deleted.
522 The device has been disabled. The device has been disabled in IoT Platform. In the IoT Platform console, check whether the device is in the Disabled state.
6100 The device does not exist. The device is not created or has been deleted. On the Device List tab of the Devices page, search for the required device to check whether the device exists.
6204 The device has been disabled. If a device is disabled, you cannot manage the device, such as adding topological relationships, setting properties, and calling services. In the IoT Platform console, check whether the device is in the Disabled state.
6287 The signature is invalid. The signature of a directly connected device or sub-device is invalid. Verify the generated signature and submitted signature by using the signature method in the Alink protocol.

For more information about the Alink protocol, see Device registration.

6288 The dynamic registration feature of the device is disabled. The Dynamic Registration switch of the product to which the sub-device belongs is turned off. On the Product Details page of the console, turn on the Dynamic Registration switch
6296 The Alibaba Cloud account information does not match the instance information. The instance does not belong to the Alibaba Cloud account. In the IoT Platform console, check whether the instance belongs to the Alibaba Cloud account.
6401 The topological relationship does not exist. The topological relationship does not exist. Log on to the IoT Platform console and choose Devices > Devices. On the page that appears, search for the device and view the device information.
6402 The gateway is the same as the sub-device when you add a topological relationship. When you add a topological relationship, you cannot attach the gateway to itself as a sub-device. Check whether the gateway is the same as the sub-device.
6619 The sub-device has been attached to another gateway. If the sub-device has been attached to another gateway, you cannot attach the sub-device to the current gateway. On the Device Information tab of the console, check whether the sub-device has been attached to a gateway.
2043 The device authentication fails because the token is invalid. The token fails to be verified during device authentication. Check whether the token has expired or is invalid. You can refresh or recreate tokens.

Message-related error codes

Message-related logs are generated in the following business scenarios:

  • Devices send messages to IoT Platform.
  • IoT Platform sends messages to devices.
  • The rules engine forwards messages by using the server-side subscription or data forwarding feature.
Error code Definition Cause Troubleshooting
1004 The format of the data that the device submits to IoT Platform is invalid. The format of the upstream data is invalid in the following OTA update scenarios:
  • The device submits OTA module versions to IoT Platform.
  • The device requests the update package information from IoT Platform
  • The device submits the update progress to IoT Platform.
Check the format of the upstream data. For more information about the data formats, see OTA updates.
1901 The message fails to be sent due to poor network conditions, such as the congestion of the TCP write buffer. The data channel between the device and the server is blocked. The probable cause is that the network transmission speed is slow, or the device cannot process this number of messages. Check network conditions and the message consumption capabilities of the device.
1902 When the message is transmitted over the network, an exception occurs. The sending failure is caused by a network exception. Check network conditions.
1903 The format of the topic is invalid. The format of the message topic is invalid. Check the topic format.
1904 IoT Platform receives an invalid RRPC response. The RRPC response received by IoT Platform does not have the corresponding RRPC request. This error may occur if the request times out. Check whether the RRPC response from the device has timed out.
1905 IoT Platform does not receive an RRPC response within the timeout period. After IoT Platform sends an RRPC request to the device, IoT Platform does not receive an RRPC response from the device within the timeout period. Check whether the device responds to the RRPC request in time.
1941 The device fails to be authenticated. The token fails to be verified. Check and reobtain the token. Then, initiate the request again.
1942 The message communication is throttled. Excessive requests are sent to the topic. Reduce the frequency of message sending from a single device or contact technical support.
1950 When the message is transmitted over the network, a network connection exception occurs. The sending failure is caused by a network exception. Check network conditions.
1951 The response type is unknown. The device sends a message of an unknown type to IoT Platform. Check the type of the message that is sent by the device. If you are using the Alibaba Cloud device SDK, contact technical support or submit a ticket.
6733 The location fails based on the network information. The device fails to be located based on the specified network information. Modify the network information and relocate the device.
6736 The location fails based on the IP address. The device fails to be located based on the specified IP address. Modify the IP address and relocate the device.
6831 The specified topic or request method does not conform to the Alink protocol. The topic to which the device submits data or the method parameter in the parsed data does not conform to the Alink protocol. Check whether the topic to which the device submits data conforms to the Alink protocol. Check whether the method parameter in the parsed data conforms to the Alink protocol.
9200 The device is inactive. The device is not activated in IoT Platform. After a new device is registered, the device is activated only after it is connected to IoT Platform and submits data to IoT Platform. Check the status of the device in the IoT Platform console.
9201 The device is disconnected. The device is disconnected from IoT Platform. Check the status of the device in the IoT Platform console.
9236 The topic fails to be authenticated. The permission that is specified for the topic is invalid. Go to the Topic List tab of the IoT Platform console. Check whether the permissions that are specified for topics are valid. The Publish permission must be specified for the topics that are used to publish messages. The Subscribe permission must be specified for the topics that are used to receive messages.
9307 The SQL statement fails to be parsed. The syntax of the SQL statement or the parameter is invalid. Check the syntax of the SQL statement and the parameters.
9324 A throttling error occurs. The requests from the device or the tenant exceed the limit. Reduce the frequency of message sending, or contact technical support.
9325 The data fails to be forwarded to the cloud service. The destination cloud service is unavailable. Check whether the destination cloud service is available.

A cloud service is unavailable if overdue payments exist, instances are deleted, or the permissions that IoT Platform use to access the cloud service are deleted.

9321 The parameters are invalid. The input parameters are invalid. Check the parameters as prompted.
9320 The payload is invalid. The format of the payload sent by the device is invalid. Check whether the format of the payload is valid.
9331 An internal error occurs on the destination cloud service. An internal error occurs on the cloud service to which the message is sent. Check the error code in the log entry, and go to the official website of the corresponding cloud service to view the cause and solution. You can also contact technical support.
9332 The cloud service configuration is invalid. The specified data forwarding destination is invalid. Therefore, an error occurs when IoT Platform connects to the destination cloud service. View the data forwarding rule to check whether the configuration of the destination cloud service is valid and whether the resource exists. Check the error code in the log entry, and go to the official website of the corresponding cloud service to view the cause and solution.
9333 The permission to access the cloud service is invalid. The permission that is granted to IoT Platform to access the destination cloud service is invalid. Check your Alibaba Cloud RAM policy.
9389 The sub-device fails to send messages because the gateway is offline. The gateway to which the sub-device is attached is offline. On the Device List tab of the Devices page, search for the required gateway and view the gateway status.

Make sure that the gateway is online, or restart the gateway to connect the sub-device with IoT Platform.

9399 An unknown internal server error occurs. IoT Platform has an internal error. Contact technical support or submit a ticket.
9600 The number of connections in a consumer group exceeds the limit. IoT Platform cannot process this number of connections. For more information, see Limits of server-side subscriptions. Clear extra connections.
9601 The heartbeat value is invalid. The heartbeat value does not meet the requirement. For more information, see. Specify a valid heartbeat value.
9602 IoT Platform ends the connection. This error may occur in the scenarios of load balancing and IoT Platform iteration. The device must be reconnected to IoT Platform. Submit a ticket.
9650 The ACK message times out. The ACK message from the receiver times out, which indicates that no response is sent from the receiver. Check the message processing logic of the receiver.
9651 The receiver returns ACK released. The receiver returns ACK released, which indicates that the received message is deleted.
9652 The receiver returns NACK. The receiver returns NACK, which indicates that the message is not received.

TSL-related error codes

TSL-related logs are generated in the following business scenarios:

  • Submit TSL data
  • Call TSL services

If the data format of a product is set to Custom, TSL-related logs include the hexadecimal values of raw data that is submitted by devices.

The following table describes error codes that may be generated when IoT Platform calls services and sets properties.

When IoT Platform calls a service, IoT Platform checks whether the input parameters of the service follow the syntax defined in the TSL model.

Error code Definition Cause Troubleshooting
100000 The parameters are invalid. The instance ID is not obtained when you query the configuration information of a product in a public or Enterprise Edition instance of IoT Platform. Check whether you have accessed an IoT Platform instance. If you have accessed an IoT Platform instance, submit a ticket for troubleshooting.
9201 The device is disconnected. The device is disconnected from IoT Platform. Check the device status in the IoT Platform console.
9200 The device is inactive. The device is not activated in IoT Platform. A newly registered device must submit data to IoT Platform before the device can be activated. Check the device status in the IoT Platform console.
9237 Overdue payments exist for the IoT Platform service. The Alibaba Cloud account has overdue payments. In the console, click Expenses in the upper-right corner and view the balance in the user center.

Make sure that the balance of your account is sufficient. Otherwise, IoT Platform devices are unavailable.

9389 The sub-device fails to send messages because the gateway is offline. The gateway to which the sub-device is attached is offline. On the Device List tab of the Devices page, search for the required gateway and view the gateway status.

Make sure that the gateway is online, or restart the gateway to connect the sub-device with IoT Platform.

6208 The device has been disabled. After a device is disabled, IoT Platform cannot set properties or call services of the device. Check the device status in the IoT Platform console. If the device is disabled, enable the device and then try again.
6300 The method parameter does not exist when IoT Platform verifies the input parameters based on the TSL model. The method parameter that is required by the Alink protocol does not exist in the standard Alink data or the parsed custom data submitted by the device. Check the submitted data by viewing the IoT Platform logs that are generated when property data is submitted. You can also check the submitted data by viewing the on-premises device logs.
6206 An error occurs when you query the service. When IoT Platform calls a service, the information about the service is queried. This error occurs if the service does not exist. Go to the Product Details page of the IoT Platform console. On the Define Feature tab, check whether the service is defined in the TSL model. If the service is defined, check whether the input parameters of the service contain invisible characters.
6200 The script does not exist. If the data format of a product is set to Custom, the script is used to parse data when IoT Platform calls the service of a device. This error occurs if you do not define a data parsing script. Go to the Product Details page of the IoT Platform console. Check whether the data parsing script exists. If the data parsing script exists, resubmit the script and then try again.
6201 The parsing result is empty. The data parsing script runs properly, but returns an empty result. For example, the rawDataToProtocol() method returns null, and the protocolToRawData() method returns null or an empty array. Check the script to identify the cause.
6207 The data format is invalid.

This error may occur when IoT Platform synchronously calls a service or when the device submits data.

When IoT Platform synchronously calls a service, this error may occur due to one of the following causes:

  • The format of the data returned by the device is invalid.
  • The format of parsed custom data is invalid.
  • The data format of the input parameters is invalid.
For information about the valid data format required by the service, see the API documentation and TSL definitions. For information about the data format required by the Alink protocol, see Alink protocol.
6330 The data format does not conform to the defined format of the Long type. The parameters or properties of the Long type are defined in the TSL model. The data format of the message does not conform to the defined format of the Long type.
  • View the logs that are generated when the device submits properties.
  • View the TSL model in the console.
6335 The parameter in the message that the device submits as a respond to the property setting request is not empty. When the device responds to the property setting request sent from IoT Platform, the response data that is indicated by the data field must be empty.
  • Check the submitted data by viewing the IoT Platform logs that are generated when property data is submitted.
  • Check the data records in the on-premises log file of the device.
5092 The property does not exist in the TSL model. The property in the upstream or downstream message is not defined in the TSL model.
Notice For a property that is defined in a custom TSL module, you must concatenate the property with the module identifier in the format of {tsl.functionBlockId}:{tsl.properties.identifier}.
  • View the logs that are generated when the device submits properties.
  • View the TSL model in the console.
5094 The service does not exist in the TSL model. The service is not defined in the TSL model, or the service parameters are invalid.
Notice For a service that is defined in a custom TSL module, you must concatenate the service with the module identifier in the format of {tsl.functionBlockId}:{tsl.service.identifier}.
  • View the logs that are generated when the device submits properties.
  • View the TSL model in the console.
5096 The event does not exist in the TSL model. The event is not defined in the TSL model, or the event parameters are invalid.
Notice For an event that is defined in a custom TSL module, you must concatenate the event with the module identifier in the format of {tsl.functionBlockId}:{tsl.event.identifier}.
  • View the logs that are generated when the device submits properties.
  • View the TSL model in the console.
System error codes
5159 An error occurs when IoT Platform retrieves the TSL property data. A system exception occurs. Submit a ticket.
5160 An error occurs when IoT Platform retrieves the TSL event data.
5161 An error occurs when IoT Platform retrieves the TSL service data.
6661 An error occurs when IoT Platform queries the tenant information.
6205 An error occurs when IoT Platform calls the service.
26015 The script parses and handles exceptions.

The following table describes the error codes that are generated when devices fail to submit property and event data.

When a device submits property or event data, IoT Platform verifies the property data or the input parameters of the event based on the TSL model.

Error code Definition Cause Troubleshooting
6106 The number of properties submitted by the device exceeds the limit. A device can submit a maximum of 200 properties at a time. Check the number of properties by viewing the IoT Platform logs that are generated when property data is submitted. You can also check the submitted data by viewing the on-premises device logs.
6300 The method parameter does not exist when IoT Platform verifies the input parameters based on the TSL model. The method parameter that is required by the Alink protocol does not exist in the standard Alink data or the parsed custom data submitted by the device. Check the submitted data by viewing the IoT Platform logs that are generated when property data is submitted. You can also check the submitted data by viewing the on-premises device logs.
6320 The property information does not exist when IoT Platform verifies the input parameters based on the TSL model. The specified property does not exist when the system queries the TSL data of the device. Go to the Product Details page of the IoT Platform console. On the Define Feature tab, check whether the specified property is defined in the TSL model. If the property is not defined, define the property.
6450 The method parameter does not exist in the Alink JSON data. The method parameter does not exist in the standard Alink data or the parsed custom data submitted by the device. View the IoT Platform logs that are generated when property data is submitted, and check whether the data includes the method parameter. You can also view the on-premises device logs.
6207 The data format is invalid.

This error may occur when IoT Platform synchronously calls the service or when the device submits data.

When the device submits data, this error may occur due to the following cause: The Alink data submitted by the device or the data parsed by using the script is not in the JSON format.

For information about the data format required by the Alink protocol, see Alink protocol. You must use the required data format to submit data.
System error codes
6452 A throttling error occurs. Traffic throttling is triggered because excessive requests are submitted. Submit a ticket.
6760 The storage quota of the tenant is exceeded. A system exception occurs. Submit a ticket.

The following table describes the error codes that are generated when devices fail to respond to the service calls and property setting requests from IoT Platform.

Error code Definition Cause Troubleshooting
Common error codes
460 The parameters are invalid. The request parameters are invalid. Submit a ticket.
500 An internal system error occurs. An unknown error occurs in IoT Platform. Submit a ticket.
400 A request error occurs. An unknown error occurs when IoT Platform calls the service. Submit a ticket.
429 Excessive requests are submitted in a specified period of time. Traffic throttling is triggered because excessive requests are submitted in a specified period of time. Submit a ticket.
System error code
6452 A throttling error occurs. Traffic throttling is triggered because excessive requests are submitted. Submit a ticket.

The following table describes the common TSL-related error codes.

IoT Platform verifies the input parameters of the service, the property data, and the input parameters of the event based on the TSL model.

Error code Definition Cause Troubleshooting
6321 The identifier of the property does not exist in the TSL model. A system exception occurs. Submit a ticket.
6317 The TSL model is invalid. A system exception occurs. Submit a ticket.
6332 The input parameter does not conform to the TSL definitions. The input parameters must conform to the TSL definitions. Go to the Product Details page of the IoT Platform console. View the TSL model on the Define Feature tab. Check the input parameters.
6302 The parameter does not exist. When IoT Platform verifies the input parameters of the service, the required parameters are not found in the request. Go to the Product Details page of the IoT Platform console. View the TSL model on the Define Feature tab. Check the input parameters of the service in the TSL model and make sure that you have specified all required parameters.
6306 The input parameter does not match the integer data type that is defined in the TSL model. When IoT Platform verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL.
  • The parameter value is not in the defined range.
Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model and make sure that the data type of the input parameter is the same as the data type defined in the TSL model.
6307 The input parameter does not match the 32-bit float data type that is defined in the TSL model. When IoT Platform verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL model.
  • The parameter value is not in the defined range.
Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model. Make sure that the data type of the input parameter is the same as the defined data type and the parameter value is in the defined value range.
6322 The input parameter does not match the 64-bit float data type that is defined in the TSL model. When IoT Platform verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL model.
  • The parameter value is not in the defined range.
Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model. Make sure that the data type of the input parameter is the same as the defined data type and the parameter value is in the defined value range.
6308 The input parameter does not match the Boolean data type that is defined in the TSL model. When IoT Platform verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL model.
  • The parameter value is not in the defined range.
Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model. Make sure that the data type of the input parameter is the same as the defined data type.
6309 The input parameter does not match the enum data type that is defined in the TSL model. The data type of the parameter is different from the data type that is defined in the TSL model. Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model. Make sure that the data type of the input parameter is the same as the defined data type.
6310 The input parameter does not match the text data type that is defined in the TSL model. When IoT Platform verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL model.
  • The length of the parameter exceeds the limit defined in the TSL model.
Go to the Product Details page of the IoT Platform console, and view the TSL model. Make sure that the data type of the input parameter is the same as the data type that is defined in the TSL model and that the parameter length does not exceed the upper limit.
6311 The input parameter does not match the date data type that is defined in the TSL model. When the system verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL model.
  • The input data is not a UTC timestamp.
Go to the Product Details page of the IoT Platform console, and view the TSL model. Make sure that the data type of the input parameter is the same as the data type that is defined in the TSL model and that the input data is a UTC timestamp.
6312 The input parameter does not match the struct data type that is defined in the TSL model. When the system verifies a parameter based on the TSL model, the following errors may occur:
  • The data type of the parameter is different from the data type that is defined in the TSL model.
  • The number of the parameters contained in a structure is different from the number defined in the TSL model.
Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model and make sure that the data type of the input parameter is the same as the data type that is defined in the TSL model.
6304 The input parameter does not exist in the TSL structure. The input parameter does not exist in the structure when IoT Platform verifies the parameter based on the TSL model. Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model and make sure that the data type of the input parameter is the same as the data type that is defined in the TSL model.
6324 The input parameter does not match the array data type that is defined in the TSL model. When the system verifies a parameter based on the TSL model, the following errors may occur:
  • The elements in the array do not follow the array syntax defined in the TSL model.
  • The number of elements in the array exceeds the maximum number defined in the TSL model.
  • Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model and check the array syntax that is defined in the TSL model.
  • View the upstream message logs to check the number of array elements in the data submitted by the device.
6328 The input parameter is not an array. The input parameter is not an array when IoT Platform verifies the parameter based on the TSL model. Go to the Product Details page of the IoT Platform console. On the Define Feature tab, view the TSL model and check the service parameter of the array data type. Make sure that the data type of the input parameter is array.
6325 The data type of elements in the array is not supported by IoT Platform. The data type of the element in the array is not supported when IoT Platform verifies the parameter based on the TSL model. Only the following data types of elements are supported: int32, float, double, text, and struct. Make sure that the data type of the element is supported by IoT Platform.
System error codes
6318 A system exception occurs when IoT Platform parses the TSL data. A system exception occurs. Submit a ticket.
6329 An error occurs when IoT Platform parses the array data in the TSL model.
6323 The data format of the parameter in the TSL model is invalid.
6316 An error occurs when IoT Platform parses the parameter in the TSL model.
6314 The data type of the parameter in the TSL model is not supported.
6301 An error occurs when IoT Platform verifies the data format of the input parameters based on the TSL model.
Data parsing script-related error codes
26010 Traffic throttling is triggered because excessive requests are submitted. The maximum number of requests in a specified period has been reached. Submit a ticket.
26001 The content of the script is empty. The script content is empty when IoT Platform runs the script. Go to the Product Details page of the IoT Platform console, and check whether the data parsing script exists. If the script exists, check whether the script is saved. The script cannot be a draft.
26002 An exception occurs when IoT Platform runs the script. The script runs properly, but the script content is invalid. For example, the script contains syntax errors. Log on to the IoT Platform console, use the same parameters to run the script for debugging, and then modify the script.
Notice The console provides a basic script running environment, but does not verify the script. We recommend that you check the script on premises before you save it.
26003 A timeout error occurs when you run the script. The logic in the script is too complex. The data is not parsed within the timeout period, which is 3 seconds. View the script content in the console and check the logic. Make sure that the script does not contain infinite loops. We recommend that you check the script on premises before you save it.
26006 The required method does not exist in the script. The script runs as expected. However, the script content is invalid. The script must contain the protocolToRawData() and rawDataToProtocol() methods. This error occurs if these two methods do not exist. Go to the Product Details page of the IoT Platform console, and check whether the protocolToRawData() and rawDataToProtocol() methods exist.
26007 The returned data format is invalid after data parsing. The script runs properly, but the format of the returned data is invalid. The script must contain the protocolToRawData() and rawDataToProtocol() methods. The protocolToRawData() method returns a byte[] array, and the rawDataToProtocol() method returns a JSON object. This error occurs if the returned data is not in the required format. For example, after a device submits data, IoT Platform sends a response to the device. The returned data must also be parsed. Otherwise, the format of the returned data may be invalid. Check the script in the IoT Platform console. Enter the input parameters, run the script on premises, and check whether the data format of the returned result is valid.

Subscription-related error codes

Error code Definition Cause Troubleshooting
9200 The device is inactive. The device is not activated on IoT Platform. After a new device is registered, the device is activated only after it is connected to IoT Platform and submits data to IoT Platform. Check the status of the device in the IoT Platform console.
500 An internal system error occurs. An unknown error occurs in IoT Platform. Submit a ticket.
403 The request is forbidden. Your account has overdue payments or the topic fails to be authenticated. Submit a ticket.

Topology-related error codes

Error code Definition Cause Troubleshooting
5005 An error occurs when you query the product information. The specified product does not exist. Log on to the IoT Platform console and choose Devices > Products. On the page that appears, query the product information and check whether the ProductKey exists.

Remote configuration-related error codes

Error code Definition Cause Troubleshooting
6710 The remote configuration file has no content. You must edit and save the file in the console, and then reobtain the file. The remote configuration file is not saved in the console. Log on the IoT Platform console and choose Maintenance > Remote Configuration. Refresh the page that appears.

Save the edited content under Configure Template.

6713 The remote configuration switch is turned off. The remote configuration switch is turned off on the Remote Configuration page. This page appears when you choose Maintenance > Remote Configuration page in the console. In the IoT Platform console, choose Maintenance > Remote Configuration. On the page that appears, check whether the remote configuration switch is turned on.