DocsICP FilingConsole
Documentation
Home Page Lindorm Developer Reference API Reference Common error codes

Common error codes

Updated at:
Copy as MD
Product
My Favorites

HTTP status code

Error code

Error message

Description

Solution

Operation

400

DiskCategoryUnsupported

The specified parameter DiskCategory is invalid.

The specified "DiskCategory" parameter is invalid. Valid values are: cloud_efficiency, cloud_ssd, local_ssd_pro, local_hdd_pro, cloud_essd, and cloud_essd_pl0.

  • Check if the value of the "DiskCategory" parameter is within the valid range.

  • See the documentation to confirm the supported disk categories.

Diagnose

400

InstanceBusying

The instance is busy, please try again later.

An operation is in progress. Try again later.

  • Try again later.

  • Wait for the current operation to complete.

Diagnose

400

DiskUsage.FetchError

Exception occurred when getting disk usage, please try again later.

An exception occurred while getting the disk usage. Try again later.

  • Try again later.

  • Contact technical support to confirm the storage service status.

Diagnose

400

StorageUsage.TooHigh

Reducing is forbidden, because the storage usage is too high.

Scale-in is prohibited because the storage usage is too high.

Increase the storage capacity.

Diagnose

403

LdfsVersion.TooLow

The minor version of ldfs is too low, please upgrade first.

The minor version of ldfs is too low. Upgrade it first.

Go to the Instance Details page in the console. In the Configuration Information section, check if the underlying storage is the latest version. If an upgrade is available, upgrade to the latest version.

Diagnose

404

RamRole.NotFound

Please authorized the Lindorm Service Linked Role.

Grant the service-linked role for Lindorm.

Check if the service-linked role for Lindorm is granted. If not, grant the role.

Diagnose

400

EnableAttachFirst.ParameterInvalid

Please enable attach cloud disk.

Enable disk attachment.

Check if the disk attachment feature is enabled. If not, enable it.

Diagnose

400

Resource.ecsResource.soldout

Insufficient resources for master nodes, please change region or available zone.

Insufficient resources for master nodes. Change the region or zone.

  • Try another region or zone.

  • Try again later.

Diagnose

400

Resource.ecsResource.soldout

Insufficient resources for core nodes, please change region or available zone.

Insufficient resources for core nodes. Change the region or zone.

  • Try another region or zone.

  • Try again later.

Diagnose

400

Resource.ecsResource.soldout

Insufficient resources for capacity cloud storage, please change region or available zone.

Insufficient storage-optimized resources. Change the region or zone.

  • Try another region or zone.

  • Try again later.

Diagnose

400

VpcOrVswitchInsufficient

Insufficient IP of VPC switch.

Insufficient IP addresses in the VPC vSwitch.

  • Check the vSwitch configuration and expand the IP address range.

  • Use a different vSwitch.

Diagnose

400

WrongParameter

Parameter wrong.

Incorrect parameter.

  • Check if the parameter format and value are correct.

  • See the API documentation to confirm the parameter requirements.

Diagnose

400

UpdateType.NotSupported

The update type is not supported.

Unsupported update type.

  • Check if the "UpdateType" parameter is correct.

  • See the documentation to confirm the supported update types.

Diagnose

403

API.Forbidden

This api is forbidden in this environment.

This API is forbidden in this environment.

  • Confirm that the environment supports this API.

  • Contact technical support to confirm the API usage permissions.

Diagnose

400

InstanceInvalid

Instance status is invalid.

The instance status is invalid.

  • Check the instance status.

  • Wait for the instance status to return to normal.

Diagnose

400

Instance.UpdateFailed

Failed to update password for user '%s' on instance %s.

Failed to update the password for user '%s' on instance %s.

  • Check the user permissions.

  • Confirm that the new password meets the requirements.

Diagnose

400

InstanceUser.DeleteFailed

Failed to delete user '%s' on instance %s.

Failed to delete user '%s' on instance %s.

  • Check if the user exists.

  • Confirm the operation permissions.

Diagnose

400

Instance.DoesNotSupportShrinkStorage

Reducing storage capacity is not supported yet.

Reducing storage capacity is not supported.

  • Confirm if the instance type supports storage scale-in.

  • Consider using a different instance type.

Diagnose

400

Instance.PleasePurchaseColdStorage

Please purchase cold storage.

Purchase cold storage.

  • Purchase the cold storage service.

  • Confirm that the cold storage configuration is correct.

Diagnose

400

Instance.PleasePurchaseArchiveStorage

Please purchase archive storage.

Purchase Archive Storage.

  • Purchase the Archive Storage service.

  • Confirm that the Archive Storage configuration is correct.

Diagnose

400

Resource.ecsResource.soldout

Insufficient resources, please change region or available zone.

Insufficient resources. Change the region or zone.

  • Try another region or zone.

  • Try again later.

Diagnose

400

InstanceUser.CreateFailed

Failed to create user '%s' on instance %s.

Failed to create user '%s' on instance %s.

  • Check if the user information is correct.

  • Confirm that the user quota is sufficient.

Diagnose

400

ReduceNodes.ParamError

Engine nodes only one is invalid, please chose more than 2 or set 0(close engine).

Having only one engine node is invalid. Select more than 2 nodes or set the number to 0 to close the engine.

  • Set the number of nodes to more than 2.

  • Or, set the number of nodes to 0 to close the engine.

Diagnose

400

ReduceNodes.ParamError

Engine nodes must be at least %s due to the activation of HDFS Erasure Coding.

The number of engine nodes must be at least %s because HDFS erasure coding is enabled.

  • Increase the number of nodes to the minimum requirement.

  • Consider disabling HDFS erasure coding.

Diagnose

400

ReduceNodes.CloudTypeParamError

Engine nodes of cloud disk type must be at least %s, and be reduced at most %s each time.

The number of engine nodes for the disk type must be at least %s. You can reduce the number of nodes by a maximum of %s at a time.

  • Ensure the number of nodes is not less than the minimum value.

  • Check that the number of nodes to reduce does not exceed the limit.

Diagnose

400

ReduceNodes.LdfsCloudTypeParamError

Engine nodes of cloud disk type must be at least %s.

The number of engine nodes for the disk type must be at least %s.

Increase the number of nodes to the minimum requirement.

Diagnose

400

ReduceNodes.LocalTypeParamError

Engine nodes of local disk type must be at least %s, and be reduced at most %s each time.

The number of engine nodes for the local disk type must be at least %s. You can reduce the number of nodes by a maximum of %s at a time.

  • Ensure the number of nodes is not less than the minimum value.

  • Check that the number of nodes to reduce does not exceed the limit.

Diagnose

400

ReduceNodes.LdfsLocalTypeParamError

Engine nodes of local disk type must be at least %s.

The number of engine nodes for the local disk type must be at least %s.

Increase the number of nodes to the minimum requirement.

Diagnose

400

ReduceNodes.LTSParamError

Engine nodes must be at least %s.

The number of engine nodes must be at least %s.

Increase the number of nodes to the minimum requirement.

Diagnose

400

Resource.Engine.Open

The number of engine nodes must be greater than 0.

The number of engine nodes must be greater than 0.

Increase the number of engine nodes to be greater than 0.

Diagnose

404

VpcCidrError

Get vpc cidr error, please contact us for more help.

Failed to get the VPC CIDR block. Contact us for help.

  • Check the VPC configuration.

  • Contact technical support for help.

Diagnose

400

InvalidParameter.%s

%s.

Invalid parameter.

  • Check if the parameter format is correct.

  • See the API documentation to confirm the parameter requirements.

  • Ensure the parameter value is within the valid range.

Diagnose

400

OperationDenied

The operation is denied, please contact us for more information.

The operation is denied. Contact us for more information.

  • Check if you have sufficient permissions to perform the operation.

  • Confirm that the operation meets system requirements.

  • Contact technical support to confirm the operation permissions.

Diagnose

400

Instance.DoesNotSupportShrinkCoreNumber

Reducing nodes is not supported yet.

Reducing the number of nodes is not supported.

  • Confirm if the instance type supports scale-in operations.

  • Consider using a different instance type.

Diagnose

400

Instance.DoesNotSupportShrinkStorage

Reducing storage capacity of log nodes is not supported yet.

Reducing the storage capacity of change data capture nodes is not supported.

  • Confirm if the instance type supports storage scale-in.

  • Consider using a different instance type.

Diagnose

403

DiskCategory.NotSupport

The time series engine and search engine does not support capacity storage. You can select standard or performance cloud storage.

LindormTSDB and search engines do not support storage-optimized storage. You can select standard or performance cloud storage.

  • Select standard or performance cloud storage.

  • See the documentation to confirm the supported storage classes.

Diagnose

500

Instance.CreationFailed

Create instance failed due to internal error.

Failed to create the instance due to an internal error.

  • Try again later.

  • Contact technical support for help.

Diagnose

500

UpgradeCapacityFailed.InternalError

Upgrade instance capacity failed due to internal error.

Failed to upgrade the instance capacity due to an internal error.

  • Try again later.

  • Contact technical support for help.

Diagnose

404

InstanceConfig.NotFound

The config of instance not found.

The instance configuration was not found.

  • Check if the instance exists.

  • Confirm that the configuration is correct.

Diagnose

400

EncryptionType.ParameterInvalid

EncryptionType is invalid.

The encryption type is invalid.

  • Check if the "EncryptionType" parameter is correct.

  • See the documentation to confirm the supported encryption types.

Diagnose

403

OperationForbidden

The operation is forbidden, please contact us for more information.

The operation is forbidden. Contact us for more information.

  • Check if you have sufficient permissions to perform the operation.

  • Contact technical support to confirm the operation permissions.

Diagnose

500

Instance.FailedAllocatingVpcIp

Failed allocating vpc ip.

Failed to allocate a VPC IP address.

  • Check if the VPC configuration has enough available IP addresses.

  • Confirm that the vSwitch configuration is correct.

  • Contact technical support to confirm the network resource status.

Diagnose

404

VSwitchInfo.NotFound

Vswitch info lost.

The vSwitch information is lost.

  • Check if the vSwitch exists.

  • Confirm that the vSwitch configuration is correct.

  • Recreate the vSwitch.

Diagnose

400

VSwitchCount.Invalid

Vswitch count is invalid.

The vSwitch count is invalid.

  • Check if the number of vSwitches is within the valid range.

  • See the documentation to confirm the vSwitch quantity requirements.

Diagnose

404

Subdomain.NotFound

Failed to get subdomain.

Failed to get the subdomain.

  • Check if the domain name configuration is correct.

  • Contact technical support to confirm the domain name service status.

Diagnose

400

PayType.IsNotValid

Pay type is not valid.

The payment type is invalid.

  • Check if the payment type parameter is correct.

  • See the documentation to confirm the supported payment types.

Diagnose

400

PayType.IsNotChanged

Pay type is not changed.

The payment type was not changed.

  • Confirm that the new payment type is different from the current one.

  • Check if the request parameters are correct.

Diagnose

400

UpgradeType.Invalid

The upgrade type parameter is invalid. Check the validity of the UpgradeType parameter.

The upgrade type parameter is invalid. Check the validity of the "UpgradeType" parameter.

  • Check if the value of the "UpgradeType" parameter is correct.

  • See the API documentation to confirm the supported upgrade types.

Diagnose

400

GenLindormV2DescFailed

Generate lindorm v2 meta data failed.

Failed to generate Lindorm V2 metadata.

  • Check if the instance configuration is correct.

  • Contact technical support to confirm the service status.

Diagnose

400

LindormV2Desc.CapacityStorageNotSupported

Capacity storage is not supported for Lindorm V2 instances.

Lindorm V2 instances do not support storage-optimized storage.

  • Select a supported storage class.

  • See the documentation to confirm the storage classes supported by Lindorm V2.

Diagnose

400

MultiChangeIsNotAllowedConcurrently

Multiple differences have been detected. Only one type of difference can be submitted at a time.

Multiple changes were detected. You can submit only one type of change at a time.

  • Submit only one type of change at a time.

  • Submit other changes after the current change is complete.

Diagnose

400

UnsupportedServiceType

The service type of the instance is unsupported.

The service type of the instance is not supported.

  • Check if the service type parameter is correct.

  • See the documentation to confirm the supported service types.

Diagnose

400

ParamsTablesInvalid

The parameter 'Tables' is empty or invalid.

The "Tables" parameter is empty or invalid.

  • Check if the "Tables" parameter is set correctly.

  • Ensure the "Tables" parameter is not empty and is in the correct format.

Diagnose

400

RestoreTimeInvalid

The restore time is invalid.

The restore time is invalid.

  • Check if the restore time format is correct.

  • Confirm that the restore time is within the valid range.

Diagnose

400

WrongTimeFormat

The time format is invalid.

The time format is invalid.

  • Check if the time format meets the requirements.

  • See the documentation to confirm the correct time format.

Diagnose

400

DescribeTypeInvalid

The describe type is invalid.

The describe type is invalid.

  • Check if the "DescribeType" parameter is correct.

  • See the documentation to confirm the supported describe types.

Diagnose

400

WhiteIpListInvalid

White IP list is invalid.

The IP whitelist is invalid.

  • Check if the IP address format is correct.

  • Ensure the IP addresses are within the valid range.

Diagnose

400

SecurityGroupListInvalid

Security group list is invalid.

The security group list is invalid.

  • Check if the security group ID format is correct.

  • Ensure the security groups exist and are valid.

Diagnose

400

ActionTypeInvalid

Action type is invalid.

The action type is invalid.

  • Check if the "ActionType" parameter is correct.

  • See the documentation to confirm the supported action types.

Diagnose

400

SecurityGroupListExceed

The num of security groups exceeds 10.

The number of security groups exceeds 10.

  • Reduce the number of associated security groups.

  • Merge security group rules.

Diagnose

400

OnlyPublicCloudAllowed

Only public cloud is allowed to do this operation.

Only public cloud environments can perform this operation.

  • Perform the operation in a public cloud environment.

  • Contact technical support to confirm the environment requirements.

Diagnose

400

Ssl.NotEnabled

SSL has not been enabled yet.

SSL is not enabled.

  • Enable the SSL feature.

  • Check if the SSL configuration is correct.

Diagnose

400

Port.Invalid

The port is invalid.

The port is invalid.

  • Check if the port number is within the valid range.

  • Confirm that the port is not in use.

Diagnose

400

RecordType.Invalid

The record type is invalid.

The record type is invalid.

  • Check if the "RecordType" parameter is correct.

  • See the documentation to confirm the supported record types.

Diagnose

400

Path.TooLong

The path is too long.

The path is too long.

  • Shorten the path length.

  • Use a shorter directory structure.

Diagnose

400

JobName.Invalid

The job name is invalid.

The job name is invalid.

  • Check if the job name format is correct.

  • Ensure the job name follows the naming conventions.

Diagnose

400

FileDir.Invalid

The file directory is invalid.

The file directory is invalid.

  • Check if the directory path is correct.

  • Ensure the directory exists and is accessible.

Diagnose

400

LdpsComponent.Invalid

The ldps component is invalid.

The ldps component is invalid.

  • Check if the component configuration is correct.

  • Confirm that the component exists.

Diagnose

400

InvalidAccount

The account is invalid.

The account is invalid.

  • Check if the account information is correct.

  • Confirm that the account exists and is valid.

Diagnose

400

WeakPassword

The password is too weak.

The password is too weak.

  • Set a strong password that meets the requirements.

  • See the password policy to set the password.

Diagnose

400

TimeWindowExceedLimit

The proactive maintenance time window must not exceed 4 hours.

The proactive maintenance time window cannot exceed 4 hours.

  • Set the maintenance time window to 4 hours or less.

  • Adjust the maintenance schedule.

Diagnose

400

Instance.IsDeleted

Instance is deleted.

The instance is deleted.

  • Confirm the instance status.

  • Recreate the instance.

Diagnose

404

Instance.NotExist

The instance does not exist. Please confirm the validity of the InstanceId parameters.

The instance does not exist. Confirm the validity of the "InstanceId" parameter.

  • Check if the "InstanceId" parameter is correct.

  • Confirm that the instance exists.

Diagnose

400

Instance.NotActive

The instance status is not running, and other operations are temporarily not allowed to be submitted.

The instance is not running. Other operations cannot be submitted at this time.

  • Wait for the instance to finish starting.

  • Check the instance status.

Diagnose

400

Instance.StatusUnknown

Instance status is unknown.

The instance status is unknown.

  • Check the instance status.

  • Contact technical support for help.

Diagnose

400

Instance.UpdateFailed

Update instance security ip list failed.

Failed to update the instance security IP list.

  • Check if the IP list format is correct.

  • Confirm the validity of the IP addresses.

Diagnose

400

SecurityGroup.UpdateFailed

Update instance security groups failed.

Failed to update the instance security groups.

  • Check the security group configuration.

  • Confirm that the security groups exist.

Diagnose

400

SecurityGroup.DescribeFailed

Describe instance security groups failed.

Failed to describe the instance security groups.

  • Check the instance status.

  • Contact technical support to confirm the service status.

Diagnose

400

Instance.UpdateFailed

Update UI account and password failed.

Failed to update the UI account and password.

  • Check if the account information is correct.

  • Confirm that the password meets the requirements.

Diagnose

400

Instance.DoesNotSupportChangeClass

Changing specifications or number of nodes is not supported yet.

Changing specifications or the number of nodes is not supported.

  • Confirm if the instance type supports change operations.

  • Consider using a different instance type.

Diagnose

400

InstanceInvalid

Only lindorm v2 instance support current operation.

Only Lindorm V2 instances support the current operation.

  • Confirm the instance type.

  • Use a Lindorm V2 instance to perform the operation.

Diagnose

400

LindormSpec.Invalid

The engine specification is invalid or unsupported.

The engine specification is invalid or unsupported.

  • Check if the engine specification parameter is correct.

  • See the documentation to confirm the supported engine specifications.

Diagnose

400

InsStorageInvalid

Storage capacity must be greater than 80GiB and a multiple of 80.

The storage capacity must be greater than 80 GiB and a multiple of 80.

  • Set the storage capacity to a value greater than 80 GiB that is a multiple of 80.

  • See the documentation to confirm the storage capacity requirements.

Diagnose

400

ReduceNodes.ParamError

Engine nodes must be at least %s, and be reduced at most %s each time.

The number of engine nodes must be at least %s. You can reduce the number of nodes by a maximum of %s at a time.

  • Ensure the number of nodes is not less than the minimum value.

  • Check that the number of nodes to reduce does not exceed the limit.

Diagnose

400

ReduceNodes.ParamError

This engine still has some data, please clear the data before closing engine.

This engine still contains data. Clear the data before you close the engine.

  • Clear the data in the engine.

  • Confirm that the data is completely deleted.

Diagnose

400

UpgradeNodes.StepSizeInvalid

The step size for node quantity adjustment is invalid. It should be a multiple of %s.

The step size for node quantity adjustment is invalid. It must be a multiple of %s.

  • Set the adjustment step size to a multiple of the specified value.

  • See the documentation to confirm the step size requirements.

Diagnose

400

EngineTypeInvalid

This engine type is invalid.

This engine type is invalid.

  • Check if the engine type parameter is correct.

  • See the documentation to confirm the supported engine types.

Diagnose

400

Order.CreateFailed

Create order failed, please contact us for more help.

Failed to create the order. Contact us for help.

  • Check if the order information is correct.

  • Contact technical support for help.

Diagnose

403

StreamVersion.TooLow

The minor version of stream engine is too low, please upgrade first.

The minor version of the stream engine is too low. Upgrade it first.

Upgrade the stream engine to the latest version.

Diagnose

403

SearchVersion.TooLow

The minor version of search engine is too low, please upgrade first.

The minor version of the search engine is too low. Upgrade it first.

Upgrade the search engine to the latest version.

Diagnose

403

LindormVersion.TooLow

The minor version of lindorm engine is too low, please upgrade first.

The minor version of the Lindorm engine is too low. Upgrade it first.

Upgrade the Lindorm engine to the latest version.

Diagnose

404

LdpsCloudVpcNotFound

Prepare compute engine resource error, please contact us for more help.

An error occurred while preparing compute engine resources. Contact us for help.

  • Check the resource configuration.

  • Contact technical support for help.

Diagnose

404

SecurityGroup.NotFound

Get cloud security groups failed.

Failed to get the cloud security groups.

  • Confirm that the security groups exist.

  • Check the security group configuration.

Diagnose

404

VswitchAcquireError

Get vswitch for spark cluster error, please contact us for more help.

An error occurred while getting the vSwitch for the Spark cluster. Contact us for help.

  • Check the network configuration.

  • Contact technical support for help.

Diagnose

404

ComputeResourceError

Prepare compute worker engine resource error, please contact us for more help.

An error occurred while preparing compute worker engine resources. Contact us for help.

  • Check the resource configuration.

  • Contact technical support for help.

Diagnose

400

SecurityGroup.CreateFailed

Create instance security groups failed, please contact us for more help.

Failed to create the instance security groups. Contact us for help.

  • Check the security group configuration.

  • Contact technical support for help.

Diagnose

400

ComputeEngine.UpdateFailed

Update compute engine resource limitation failed, please contact us for more help.

Failed to update the compute engine resource limits. Contact us for help.

  • Check the resource configuration.

  • Contact technical support for help.

Diagnose

400

SLR.CreateError

Create serivce linked role error, please contact us for more help.

An error occurred while creating the service-linked role. Contact us for help.

  • Check the role configuration.

  • Contact technical support for help.

Diagnose

404

ComputeEngine.JobNotFound

This job not found.

This job was not found.

  • Confirm that the job exists.

  • Check if the job ID is correct.

Diagnose

400

Tags.ExceedLimitation

The number of tags exceeds the limit, the maximum is %s.

The number of tags exceeds the limit. The maximum is %s.

  • Reduce the number of tags to be within the limit.

  • Merge similar tags.

Diagnose

400

InvalidTagKey.Malformed

The specified parameter "Tag.n.Key" is not valid.

The specified parameter "Tag.n.Key" is invalid.

  • Check if the tag key format is correct.

  • See the documentation to confirm the tag key requirements.

Diagnose

400

Duplicate.TagKey

The specified parameter "Tag.n.Key" is duplicated.

The specified parameter "Tag.n.Key" is a duplicate.

  • Ensure that tag keys are unique.

  • Modify the duplicate tag keys.

Diagnose

400

InvalidParameter.ResourceType

The specified parameter "ResourceType" is not valid.

The specified parameter "ResourceType" is invalid.

  • Check if the "ResourceType" parameter is correct.

  • See the documentation to confirm the supported resource types.

Diagnose

400

InvalidParameter.ResourceId

The specified parameter "ResourceId.n" is not valid.

The specified parameter "ResourceId.n" is invalid.

  • Confirm that the resource exists.

  • Check if the "ResourceId" parameter is correct.

Diagnose

400

NumberExceed.ResourceIds

The number of ResourceIds exceeds the limit, the maximum is %s.

The number of ResourceIds exceeds the limit. The maximum is %s.

Reduce the number of ResourceIds to be within the limit.

Diagnose

400

InvalidParameter.ApiVersionMismatch

The input instance serviceType %s does not match the api version %s, you should call api %s.

The input instance serviceType %s does not match the API version %s. You must call API %s.

  • Call the interface using the correct API version.

  • Confirm that the instance serviceType matches the API version.

Diagnose

400

AutoScaleRequest.Failed

Request to autoScaler service failed.

The request to the auto-scaler service failed.

  • Check the auto-scaler service status.

  • Confirm that the request parameters are correct.

Diagnose

400

InvalidParameter.CronExpr

Cron expression is invalid.

The cron expression is invalid.

  • Check if the cron expression format is correct.

  • See the documentation to confirm the cron expression requirements.

Diagnose

400

GrantAclFailed

Failed to grant ACL for user '%s' on instance %s.

Failed to grant the ACL for user '%s' on instance %s.

  • Check the user permissions.

  • Confirm the instance status.

Diagnose

400

RevokeAclFailed

Failed to revoke ACL for user '%s' on instance %s.

Failed to revoke the ACL for user '%s' on instance %s.

  • Confirm the instance status.

  • Check the user permissions.

Diagnose

400

Forbidden.RegionNotFound

The provided RegionId does not match to the endpoint.

The operation failed. The provided RegionId does not match the endpoint.

Switch the endpoint to the same region.

Diagnose

499

OperationFailed

The operation processing has failed due to some unknown error or exception, please contact us or submit a ticket for help.

The operation failed due to an unknown error or exception. Contact us or submit a ticket for help.

  • An unknown error or exception occurred. Try again later.

  • If the error persists, contact support or submit a ticket.

Diagnose

400

SecurityIpStatus.NotActive

Security Ip Status Not Active.

The instance security group or whitelist is being updated. Try again later.

  • Refresh the page and try again.

  • If the operation fails after multiple retries, contact technical support for help.

Diagnose

400

LindormErrorCode.%s

%s.

A generic error code was returned. For more information, see the error message.

Modify your request parameters based on the error message and the OpenAPI documentation, and then try the request again. For more information, see the API Documentation Center.

Diagnose

Previous：Release notesNext：API usage examples