All Products
Search
Document Center

ApsaraMQ for RocketMQ:Public error codes

Last Updated:Jul 31, 2025

Error code

HTTP status codeError codeError messageDescriptionActions
500InternalErrorAn error occurred while processing your request. Please submit the work order.A system exception occurred. Please submit a ticket.diagnosis
500RemoteCallErrorAn internal service invocation error occurred while processing your request. Please try again later.An internal service invocation error occurred. Please try again later.diagnosis
404AsyncTask.NotFoundThe asynchronous task does not exist.The asynchronous task does not exist.diagnosis
400AsyncTask.InOrderThe asynchronous task appending.The asynchronous task is in queue.diagnosis
404AsyncTaskType.NotFoundThe asynchronous task type does not exist.The type of the asynchronous task does not exist.diagnosis
404AsyncTaskGroup.NotFoundThe asynchronous task group does not exist.The group of the asynchronous task does not exist.diagnosis
404AsyncTaskHandler.NotFoundThe asynchronous task executor does not exist.The executor of the asynchronous task does not exist.diagnosis
400AsyncTaskSlave.NotCompletedThe asynchronous sub task not complete yet.The subtask of the asynchronous task is not completed.diagnosis
400AsyncTask.IgnoredThe asynchronous task ignored.Execution of the asynchronous task is ignored.diagnosis
400AsyncTask.NotCompletedThe asynchronous task not complete yet.The asynchronous task is not completed.diagnosis
400DateFormatErrorThe date format error.An exception occurred during time conversion.diagnosis
400RamResourceErrorThe ram resource error.An RAM resource exception occurred.diagnosis
403NoPermissionPermission deniedYou do not have the permissions.diagnosis
400Order.ExistedThe order already exists.The order already exists.diagnosis
404Order.NotFoundThe order cannot be found.The order cannot be found.diagnosis
400OrderType.NotSupportThe order type not supported.The order type is not supported.diagnosis
400Ability.ExistedThe ability already exsits.The ability already exists.diagnosis
404Ability.NotFoundThe ability cannot be found.The ability does not exist.diagnosis
400AbilityStatus.NotPendingThe ability has yet to take effect.The ability is not in the pending state.diagnosis
400Commodity.ExistedThe commodity already exists.The product already exists.diagnosis
404Commodity.NotFoundThe commodity cannot be found.The product does not exist.diagnosis
400CommodityStatus.NotPendingThe commodity is not pending.The product is not in the pending state.diagnosis
400CommodityStatus.NotValidThe commodity has yet to take effect.The product is not in effect.diagnosis
400Instance.ExistedThe instance already exists.The instance already exists.diagnosis
404Instance.NotFoundThe instance cannot be found.The instance does not exist.diagnosis
400InstanceId.NotNullThe instanceId is mandatory for this action.The instance ID cannot be empty.diagnosis
400InstanceStatus.ReleasedThe instance already released.The instance is released.diagnosis
400InstanceStatus.StoppedThe instance already stopped.The instance is terminated.diagnosis
400InstanceStatus.NotRunningThe instance is not running.The instance is not running.diagnosis
400InstanceStatus.NotAllowedThe operation is forbidden for current instance states.You cannot modify the current status of the instance.diagnosis
403InstanceUser.NotBelongThe instance does not belong to the current userThe instance does not belong to the current user.diagnosis
400InstanceRelease.NotSupportThe current instance type does not support the release operationThe instance cannot be released.diagnosis
400Service.ExistedThe service already exists.The service already exists.diagnosis
404Service.NotFoundThe service cannot be found.The service does not exist.diagnosis
404ServiceMsgProcessSpec.NotFoundThe message process spec cannot be found.The computing specification for messaging does not exist.diagnosis
400ServiceSeries.NotNullThe serviceSeries is mandatory for this action.The service series cannot be empty.diagnosis
400ServiceSeries.ExistedThe serviceSeries already exists.The service series already exists.diagnosis
404ServiceSeries.NotFoundThe serviceSeries cannot be found.The service series does not exist.diagnosis
400ServiceSeriesStatus.NotPendingThe serviceSeries is not pending.The service series is not in the pending state.diagnosis
400ServiceSeriesStatus.NotValidThe serviceSeries does not take effect.The service series is not in effect.diagnosis
400StsCertificate.NotNullThe sts certificate is mandatory for this action.The STS certificate cannot be empty.diagnosis
400MeterRecord.ExistedThe meterRecord already exists.The metering record already exists.diagnosis
404Topic.NotFoundThe topic cannot be found.The topic does not exist.diagnosis
400Topic.ExistedThe topic already exists.The topic is already created.diagnosis
400TopicStatus.notRunningThe topic is not running.The topic is not running.diagnosis
400TopicCount.LimitedThe topic quantity over limitThe number of topics exceeds the capacity.diagnosis
400TopicName.NotStandardThe topic name is invalid.The topic name is non-standard.diagnosis
400TopicName.SystemThe topic name has been reserved by the system.The topic name is occupied in the system.diagnosis
400ConsumerGroupCount.LimitedThe group quantity over limitThe number of groups exceeds the capacity.diagnosis
400GroupName.canSystemReservedThe group name has been reserved by the system.The group name is occupied in the system.diagnosis
404ConsumerGroup.NotFoundThe consumerGroup cannot be found.The group does not exist.diagnosis
400ConsumerGroup.ExistedThe consumerGroup already exists.The group is already created.diagnosis
400ConsumerGroupStatus.NotRunningThe consumerGroup is not running.The group is not running.diagnosis
400TraceRecord.ExistedThe trace record already exists.The trace record is already created.diagnosis
404TraceRecord.NotFoundThe trace record cannot be found.The trace record does not exist.diagnosis
404TraceResult.notFoundThe trace result already exists.-diagnosis
400TraceResult.ExistedThe trace result cannot be found.-diagnosis
400MessageSendTopic.NotSupportThe current messageType is not supported.Messages of this topic cannot be sent.diagnosis
400ResourceTagService.ErrorFailed to manipulate the resource tag.Failed to manipulate resource tagdiagnosis
400DisasterRecoveryPlan.DuplicateThe disaster recovery task cannot contain two identical instances.-diagnosis
404Resource.NotFoundThe resource is not found.The resource is not found.diagnosis
400InstanceApacheAcl.NotSupportinstance does not support acl identification.instance does not support acl identificationdiagnosis
400DisasterRecoveryRegion.NotSupportThe region of the instance in the disaster recovery plan is not supported.The region of the instance in the disaster recovery plan is not supported.diagnosis
400DisasterRecoveryInstance.NotEmptyThe instance information in the disaster recovery plan cannot be empty.-diagnosis
400DisasterRecoveryInstance.NotSupportChangeThe instances in the disaster recovery plan do not support to change.-diagnosis
400DisasterRecoveryInstancePrivateIp.NotSupportIn the disaster recovery instance information, if the network is set to public, private IP addresses are not supported.-diagnosis
400DisasterRecoveryInstanceAliyun.AtLeastOneThe disaster recovery plan instance information must include at least one Alibaba Cloud instance.-diagnosis
400DisasterRecoveryInstanceSize.ErrorThe disaster recovery plan must include exactly two instances.-diagnosis
400DisasterRecoveryCrossBorder.NotSupportThe disaster recovery plan does not support cross-border synchronization.-diagnosis
404DisasterRecoveryPlan.NotFoundThe disaster recovery plan does not exist.-diagnosis
400DisasterRecoveryTopic.SizeErrorThe number of Topics in the disaster recovery item is exactly two.-diagnosis
400DisasterRecoveryTopicConsumerGroup.IsUsedThe consumer group used in this disaster recovery item has already been utilized.-diagnosis
403DisasterRecoveryPlanUser.NotBelongThe disaster recovery plan does not belong to the current user.-diagnosis
400DisasterRecoveryMessagePropertyKey.NotMatchIn the disaster recovery plan, the message property key for different instances must be consistent.-diagnosis
400DisasterRecoveryMessagePropertyKey.MustSameIn different disaster recovery plans, the message property key for the same instance must remain consistent.-diagnosis
400DisasterRecoveryItem.NotAllDeletedThe disaster recovery plan items have not been completely deleted.-diagnosis
400DisasterRecoveryPlanName.RepeatThe disaster recovery plan name already exists.-diagnosis
404DisasterRecoveryItem.NotFoundThe disaster recovery plan item does not exist.-diagnosis
400DisasterRecoveryRegion.NotSupportOperateThe current region does not support operations for this disaster recovery plan.-diagnosis
400DisasterRecoveryPlanSameDirection.NotSupportThe synchronization of disaster recovery plan instances in the same direction does not support duplication.-diagnosis
400DisasterRecoveryItemStatus.ErrorThe current status of the disaster recovery item does not support this operation.-diagnosis
400DisasterRecoveryPlanStatus.ErrorThe current status of the disaster recovery plan does not support this operation.-diagnosis
400DisasterRecoveryItem.DuplicatedIn the disaster recovery plan items, the Topic cannot be duplicated.-diagnosis
400DisasterRecoveryActiveTopic.DuplicatedIn the disaster recovery plan items, the topics in the source cluster cannot be duplicated.-diagnosis
400DisasterRecoveryPlanType.UpdateNotSupportThe disaster recovery plan does not support updating the plan type.-diagnosis
400DisasterRecoveryTopicConsumerGroup.TooLongThe consumer group generated based on the topic name is too long, and creating a disaster recovery task is not supported.-diagnosis
400DisasterRecoveryItem.InstanceErrorThe instance information transmitted in the disaster recovery item is incorrect.-diagnosis
400DisasterRecoveryMessagePropertyValue.NOT_SAMEThe filter value cannot be consistent between instances in the backup plan.The filter value cannot be consistent between instances in the backup plan.diagnosis
400DisasterRecoveryInstanceSeriesType.NotSupportThe primary family of the instance in the backup plan does not support.The primary family of the instance in the backup plan does not supportdiagnosis