¶ Error Code
The error code message format is as follows:
{
message: 'The system is busy, please try again later',
code: 1000,
data: null
}
Code | Description |
---|---|
1000 | The system is busy, please try again later |
1001 | No permission to perform this operation |
2000 | The account is abnormal, you need to enter the verification code |
2001 | Verification code verification failed (verification code error) |
2002 | Monthly login quota exceeded. Contact sales for upgrade. |
2003 | E-mail format incorrect |
2004 | User does not exist |
2005 | User has been locked |
2006 | Incorrect password |
2007 | Illegal application name |
2008 | Already have an app with the same name |
2009 | Illegal application type |
2010 | The ID of the application that needs to provide the operation |
2011 | Application does not exist |
2012 | Default user group is missing |
2013 | Illegal application description |
2014 | Incorrect input format when searching for users |
2015 | Illegal search type when searching for users |
2016 | Client password decryption error |
2017 | Mail to resolve this mode of meta_data (macro) command error |
2018 | The user does not have permission to modify this item |
2019 | erification is required when changing the password |
2020 | Not logged in yet, no permission to access this request |
2021 | Failed to send mail, reason: unable to get mail template |
2022 | User email verification failed, reason: unable to get email template |
2023 | User mailbox verification failed, reason: verification link has expired and needs to be resent |
2024 | Project description cannot exceed 140 words |
2025 | Use the default mail service provider error |
2026 | The user already exists, please do not register again |
2027 | Registered with OAuth, but tried to log in with a password. The password is not set and cannot be verified. Please log in with OAuth |
2028 | Please provide the correct phone number or email address |
2029 | Password length cannot be less than 6 digits |
2030 | No more than 80 users can be queried at a time |
2031 | App has banned user registration |
2032 | Password required for registration |
2034 | Password required for registration |
2035 | Mobile phone number has been bound |
2036 | User does not belong to this user pool |
2037 | The filled-in old mailbox does not match the actual mailbox |
2038 | The filled-in old phone does not match the actual phone |
2039 | Domain name is already used |
2040 | MAU quota exceeded |
2100 | Request rate exceeded, please try again later |
2101 | Please provide the app ID |
2200 | Mailbox already exists |
2201 | Please enter the original password |
2202 | The modified information does not belong to the current user |
2203 | The original password is wrong |
2204 | E-mail format is incorrect |
2205 | Missing parameter:registerInClient |
2206 | Login information has expired, need to log in again |
2207 | The login information is wrong, need to log in again |
2209 | No permission to delete this user |
2210 | A wrong delete operation was performed, which may be caused by deleting a non-existent user, or other errors occurred during the deletion. |
2211 | Missing parameter:username |
2212 | Cannot delete root user |
2213 | When trying to bind a third-party OAuth login method, it has already been bound |
2214 | Failed to read the bound OAuth login method |
2215 | When trying to bind a third-party OAuth login method, the account has already been bound |
2216 | When trying to unbind the third-party OAuth login method, no bounding exists |
2217 | When trying to unbind the third-party OAuth login method or mailbox, there is only one login method, so it cannot be unbind |
2218 | When trying to modify the password, the mailbox is not bound, and modification is not allowed |
2219 | When trying to unbind the mailbox, the user did not bind the mailbox |
2220 | When trying to create or update an OAuth application, this application name already exists |
2221 | When trying to update the OAuth app, the app does not exist |
2222 | When trying to create or update OAuth application information, a reserved domain name was used |
2223 | When trying to create OAuth application information, a used domain name was used |
2224 | User pool does not exist |
2225 | The updateUser interface cannot directly modify the mailbox, please use the updateEmail interface |
2226 | The updateUser API cannot directly modify the phone number, please use the updatePhone interface |
2227 | To modify the mailbox, the original mailbox must be verified |
2229 | The new mailbox is the same as the old mailbox |
2230 | The new mailbox is the same as the old mailbox |
2231 | Invalid request. Insufficient request parameter! |
2300 | Verification code expired |
2401 | Mobile application sso session does not exist |
3012 | Macro execution error |
3013 | Sending mail error, unknown error |
3014 | Failed to send mail. Reason: unable to contact SMTP transport server |
3617 | No permission to add collaborators |
3619 | No permission to view the collaborated userpool information |
3620 | Collaborator already exists |
3621 | No permission to delete collaboration |
3622 | No permission to view list of collaborators |
3623 | No collaboration relationship |
3624 | No permission to modify collaborators |
3829 | Subdomain already exists |
4212 | OIDC application does not exist |
5000 | Failed to obtain the corresponding application of the order |
5001 | Order does not exist |
5022 | Failed to create order |
5023 | Failed to create Alipay order |
5024 | Failed to create order: unknown error |
5025 | Failed to create order: incorrect amount format |
7348 | SAML SP application does not exist |
8128 | An error occurred when returning saml assertion |