错误信息参考
有关如何使用异常和错误代码的更多信息，请参阅 处理异常和错误。
¥For more information about how to work with exceptions and error codes, see Handling exceptions and errors.
Prisma 客户端错误类型
¥Prisma Client error types
Prisma 客户端会抛出不同类型的错误。下面列出了异常类型及其记录的数据字段：
¥Prisma Client throws different kinds of errors. The following lists the exception types, and their documented data fields:
PrismaClientKnownRequestError
如果查询引擎返回与请求相关的已知错误，Prisma 客户端将引发 PrismaClientKnownRequestError 异常 - 例如，违反唯一约束。
¥Prisma Client throws a PrismaClientKnownRequestError exception if the query engine returns a known error related to the request - for example, a unique constraint violation.
| 属性 | 描述 |
|---|---|
code | Prisma 专用的 错误代码。 |
meta | 有关错误的附加信息 - 例如，导致错误的字段：{ target: [ 'email' ] } |
message | 与 错误代码 相关的错误消息。 |
clientVersion | Prisma 客户端版本（例如 2.19.0） |
PrismaClientUnknownRequestError
如果查询引擎返回与没有错误代码的请求相关的错误，Prisma 客户端将引发 PrismaClientUnknownRequestError 异常。
¥Prisma Client throws a PrismaClientUnknownRequestError exception if the query engine returns an error related to a request that does not have an error code.
| 属性 | 描述 |
|---|---|
message | 与 错误代码 相关的错误消息。 |
clientVersion | Prisma 客户端版本（例如 2.19.0） |
PrismaClientRustPanicError
如果底层引擎崩溃并以非零退出代码退出，Prisma Client 会引发 PrismaClientRustPanicError 异常。在这种情况下，Prisma Client 或整个 Node 进程必须重新启动。
¥Prisma Client throws a PrismaClientRustPanicError exception if the underlying engine crashes and exits with a non-zero exit code. In this case, Prisma Client or the whole Node process must be restarted.
| 属性 | 描述 |
|---|---|
message | 与 错误代码 相关的错误消息。 |
clientVersion | Prisma 客户端版本（例如 2.19.0） |
PrismaClientInitializationError
如果启动查询引擎并创建与数据库的连接时出现问题，Prisma Client 会抛出 PrismaClientInitializationError 异常。这种情况发生在：
¥Prisma Client throws a PrismaClientInitializationError exception if something goes wrong when the query engine is started and the connection to the database is created. This happens either:
-
当
prisma.$connect()被调用时 OR¥When
prisma.$connect()is called OR -
当执行第一个查询时
¥When the first query is executed
可能发生的错误包括：
¥Errors that can occur include:
-
提供的数据库凭据无效
¥The provided credentials for the database are invalid
-
提供的主机名和端口下没有运行数据库服务器
¥There is no database server running under the provided hostname and port
-
查询引擎 HTTP 服务器想要绑定的端口已被占用
¥The port that the query engine HTTP server wants to bind to is already taken
-
环境变量丢失或无法访问
¥A missing or inaccessible environment variable
-
无法找到当前平台的查询引擎二进制文件（
generator块）¥The query engine binary for the current platform could not be found (
generatorblock)
| 属性 | 描述 |
|---|---|
errorCode | Prisma 特定的错误代码。 |
message | 与 错误代码 相关的错误消息。 |
clientVersion | Prisma 客户端版本（例如 2.19.0） |
PrismaClientValidationError
如果验证失败，Prisma 客户端会抛出 PrismaClientValidationError 异常 - 例如：
¥Prisma Client throws a PrismaClientValidationError exception if validation fails - for example:
-
缺失字段 - 例如，创建新记录时的空
data: {}属性¥Missing field - for example, an empty
data: {}property when creating a new record -
提供的字段类型不正确（例如，将
Boolean字段设置为"Hello, I like cheese and gold!"）¥Incorrect field type provided (for example, setting a
Booleanfield to"Hello, I like cheese and gold!")
| 属性 | 描述 |
|---|---|
message | 错误信息。 |
clientVersion | Prisma 客户端版本（例如 2.19.0） |
错误代码
¥Error codes
常见的
¥Common
P1000
“针对 {database_host} 处的数据库服务器的身份验证失败，为 {database_user} 提供的数据库凭据无效。请确保为 {database_host} 的数据库服务器提供有效的数据库凭据。”
¥"Authentication failed against database server at {database_host}, the provided database credentials for {database_user} are not valid. Please make sure to provide valid database credentials for the database server at {database_host}."
P1001
“无法到达 {database_host}:{database_port} 的数据库服务器，请确保你的数据库服务器正在 {database_host}:{database_port} 运行。”
¥"Can't reach database server at {database_host}:{database_port} Please make sure your database server is running at {database_host}:{database_port}."
P1002
“已到达 {database_host}:{database_port} 的数据库服务器，但超时。请再试一次。请确保你的数据库服务器正在 {database_host}:{database_port} 运行。"
¥"The database server at {database_host}:{database_port} was reached but timed out. Please try again. Please make sure your database server is running at {database_host}:{database_port}. "
P1003
"数据库 {database_file_name} 不存在于 {database_file_path}"
¥"Database {database_file_name} does not exist at {database_file_path}"
“数据库 {database_name}.{database_schema_name} 在 {database_host}:{database_port} 的数据库服务器上不存在。”
¥"Database {database_name}.{database_schema_name} does not exist on the database server at {database_host}:{database_port}."
“数据库 {database_name} 在 {database_host}:{database_port} 的数据库服务器上不存在。”
¥"Database {database_name} does not exist on the database server at {database_host}:{database_port}."
P1008
“{time} 之后操作超时”
¥"Operations timed out after {time}"
P1009
“数据库 {database_name} 已存在于 {database_host}:{database_port} 的数据库服务器上”
¥"Database {database_name} already exists on the database server at {database_host}:{database_port}"
P1010
“用户 {database_user} 被拒绝访问数据库 {database_name}”
¥"User {database_user} was denied access on the database {database_name}"
P1011
“打开 TLS 连接时出错：---左括号---消息}"
¥"Error opening a TLS connection: {message}"
P1012
注意：如果将 Prisma ORM 升级到版本 4.0.0 或更高版本后收到错误代码 P1012，请参阅 4.0.0 版本升级指南。在版本 4.0.0 之前有效的架构可能在版本 4.0.0 及更高版本中无效。升级指南解释了如何更新架构以使其有效。
¥Note: If you get error code P1012 after you upgrade Prisma ORM to version 4.0.0 or later, see the version 4.0.0 upgrade guide. A schema that was valid before version 4.0.0 might be invalid in version 4.0.0 and later. The upgrade guide explains how to update your schema to make it valid.
"---左括号---full_error}"
¥"{full_error}"
可能的 P1012 错误消息：
¥Possible P1012 error messages:
-
“参数
{}丢失。”¥"Argument
{}is missing." -
“函数
{}采用 个参数，但收到了 。”¥"Function
{}takes arguments, but received ." -
“属性
@{}中缺少参数{}。”¥"Argument
{}is missing in attribute@{}." -
“数据源块
{}中缺少参数{}。”¥"Argument
{}is missing in data source block{}." -
“生成器组
{}中缺少参数{}。”¥"Argument
{}is missing in generator block{}." -
“解析属性
@{}时出错："¥"Error parsing attribute
@{}: " -
“属性
@{}被定义了两次。”¥"Attribute
@{}is defined twice." -
“无法定义数据库名为
{}的模型，因为存在另一个具有该名称的模型：{}"¥"The model with database name
{}could not be defined because another model with this name exists:{}" -
“
{}是保留的标量类型名称，不能使用。”¥"
{}is a reserved scalar type name and can not be used." -
“无法定义
{}，因为具有该名称的 已存在。”¥"The
{}cannot be defined because a with that name already exists." -
“密钥
{}已在 中定义。”¥"Key
{}is already defined in ." -
“参数
{}已指定为未命名参数。”¥"Argument
{}is already specified as unnamed argument." -
“参数
{}已指定。”¥"Argument
{}is already specified." -
"没有这样的说法。""
¥"No such argument.""
-
“字段
{}已在模型{}上定义。”¥"Field
{}is already defined on model{}." -
“模型
{}中的字段{}不能是列表。当前连接器不支持原始类型列表。”¥"Field
{}in model{}can't be a list. The current connector does not support lists of primitive types." -
“索引名称
{}已声明多次。使用当前的连接器索引名称必须是全局唯一的。”¥"The index name
{}is declared multiple times. With the current connector index names have to be globally unique." -
“值
{}已在枚举{}上定义。”¥"Value
{}is already defined on enum{}." -
“属性未知：
@{}."¥"Attribute not known:
@{}." -
“功能未知：
{}."¥"Function not known:
{}." -
“数据源提供商未知：
{}."¥"Datasource provider not known:
{}." -
“shadowDatabaseUrl 与数据源
{}的 url 相同。请指定不同的数据库作为影子数据库。”¥"shadowDatabaseUrl is the same as url for datasource
{}. Please specify a different database as shadow database." -
“预览功能
{}未知。预期其中之一："¥"The preview feature
{}is not known. Expected one of: " -
“
{}不是 的有效值。”¥"
{}is not a valid value for ." -
“类型
{}既不是内置类型，也不是指其他模型、自定义类型或枚举。”¥"Type
{}is neither a built-in type, nor refers to another model, custom type, or enum." -
“
{}型不是内置型。”¥"Type
{}is not a built-in type." -
“意外的标记。预期其中之一："
¥"Unexpected token. Expected one of: "
-
“未找到环境变量：."
¥"Environment variable not found: ."
-
“预期为 值，但收到 值
{}。”¥"Expected a value, but received value
{}." -
“预期为 值，但解析
{}时失败：."¥"Expected a value, but failed while parsing
{}: ." -
“验证模型
{}时出错："¥"Error validating model
{}: " -
“验证模型
{}中的字段{}时出错："¥"Error validating field
{}in model{}: " -
“验证数据源
{datasource}时出错：---左括号---消息}"¥"Error validating datasource
{datasource}: {message}" -
“验证枚举
{}时出错："¥"Error validating enum
{}: " -
“验证错误："
¥"Error validating: "
P1013
“提供的数据库字符串无效。---左括号---详细信息}"
¥"The provided database string is invalid. {details}"
P1014
“模型 {model} 的底层 {kind} 不存在。”
¥"The underlying {kind} for model {model} does not exist."
P1015
“你的 Prisma 架构正在使用该数据库版本不支持的功能。
数据库版本：{database_version}
Errors:
{错误}"
¥"Your Prisma schema is using features that are not supported for the version of the database.
Database version: {database_version}
Errors:
{errors}"
P1016
“你的原始查询的参数数量不正确。预期的：{expected}，实际：{actual}."
¥"Your raw query had an incorrect number of parameters. Expected: {expected}, actual: {actual}."
P1017
"服务器已关闭连接。"
¥"Server has closed the connection."
Prisma 客户端（查询引擎）
¥Prisma Client (Query Engine)
P2000
“为该列提供的值对于该列的类型来说太长。柱子：---左括号---column_name}"
¥"The provided value for the column is too long for the column's type. Column: {column_name}"
P2001
“where 条件({model_name}.{argument_name} = {argument_value})中查找到的记录不存在”
¥"The record searched for in the where condition ({model_name}.{argument_name} = {argument_value}) does not exist"
P2002
"唯一约束在 {constraint 上失败}"
¥"Unique constraint failed on the {constraint}"
P2003
“该字段的外键约束失败：{field_name}"
¥"Foreign key constraint failed on the field: {field_name}"
P2004
“数据库上的约束失败：{database_error}"
¥"A constraint failed on the database: {database_error}"
P2005
“数据库中存储的字段 {field_name} 的值 {field_value} 对于该字段的类型无效”
¥"The value {field_value} stored in the database for the field {field_name} is invalid for the field's type"
P2006
“为 {model_name} 字段 {field_name} 提供的值 {field_value} 无效”
¥"The provided value {field_value} for {model_name} field {field_name} is not valid"
P2007
“数据验证错误 {database_error}”
¥"Data validation error {database_error}"
P2008
“无法解析 {query_position} 处的查询 {query_parsing_error}”
¥"Failed to parse the query {query_parsing_error} at {query_position}"
P2009
“无法验证查询：{query_validation_error} 于 {query_position}"
¥"Failed to validate the query: {query_validation_error} at {query_position}"
P2010
“原始查询失败。代码：{code}。信息：{message}"
¥"Raw query failed. Code: {code}. Message: {message}"
P2011
"{constraint 上的空约束违规}"
¥"Null constraint violation on the {constraint}"
P2012
“缺少 {path} 处所需的值”
¥"Missing a required value at {path}"
P2013
“缺少 {object_name} 上字段 {field_name} 所需的参数 {argument_name}。”
¥"Missing the required argument {argument_name} for field {field_name} on {object_name}."
P2014
“你尝试进行的更改将违反 {model_a_name} 和 {model_b_name} 模型之间所需的关系 '{relation_name}'。”
¥"The change you are trying to make would violate the required relation '{relation_name}' between the {model_a_name} and {model_b_name} models."
P2015
“找不到相关记录。---左括号---详细信息}"
¥"A related record could not be found. {details}"
P2016
“查询解释错误。---左括号---详细信息}"
¥"Query interpretation error. {details}"
P2017
“{parent_name} 和 {child_name} 模型之间的关系 {relation_name} 的记录未连接。”
¥"The records for relation {relation_name} between the {parent_name} and {child_name} models are not connected."
P2018
“未找到所需的连接记录。---左括号---详细信息}"
¥"The required connected records were not found. {details}"
P2019
“输入错误。---左括号---详细信息}"
¥"Input error. {details}"
P2020
“值超出该类型的范围。---左括号---详细信息}"
¥"Value out of range for the type. {details}"
P2021
“当前数据库中不存在表 {table}。”
¥"The table {table} does not exist in the current database."
P2022
“当前数据库中不存在 {column} 列。”
¥"The column {column} does not exist in the current database."
P2023
“列数据不一致：---左括号---消息}"
¥"Inconsistent column data: {message}"
P2024
“从连接池获取新连接超时。（更多信息：http://pris.ly/d/connection-pool（当前连接池超时：{timeout}，连接限制：{connection_limit}）”
¥"Timed out fetching a new connection from the connection pool. (More info: http://pris.ly/d/connection-pool (Current connection pool timeout: {timeout}, connection limit: {connection_limit})"
P2025
“操作失败，因为它依赖于需要但未找到的一条或多条记录。---左撑---原因}"
¥"An operation failed because it depends on one or more records that were required but not found. {cause}"
P2026
“当前的数据库提供程序不支持查询使用的功能：---左支撑---功能}"
¥"The current database provider doesn't support a feature that the query used: {feature}"
P2027
“查询执行期间数据库发生多个错误：---左括号---错误}"
¥"Multiple errors occurred on the database during query execution: {errors}"
P2028
“事务 API 错误：---左括号---错误}"
¥"Transaction API error: {error}"
P2029
“超出查询参数限制错误：---左括号---消息}"
¥"Query parameter limit exceeded error: {message}"
P2030
"找不到用于搜索的全文索引，请尝试将 @@fulltext([Fields...]) 添加到你的架构中"
¥"Cannot find a fulltext index to use for the search, try adding a @@fulltext([Fields...]) to your schema"
P2031
“Prisma 需要执行事务，这需要你的 MongoDB 服务器作为副本集运行。查看具体信息：https://pris.ly/d/mongodb-replica-set"
¥"Prisma needs to perform transactions, which requires your MongoDB server to be run as a replica set. See details: https://pris.ly/d/mongodb-replica-set"
P2033
“查询中使用的数字不适合 64 位有符号整数。如果你尝试存储大整数，请考虑使用 BigInt 作为字段类型”
¥"A number used in the query does not fit into a 64 bit signed integer. Consider using BigInt as field type if you're trying to store large integers"
P2034
“由于写入冲突或死锁，事务失败。请重试你的事务”
¥"Transaction failed due to a write conflict or a deadlock. Please retry your transaction"
P2035
“数据库上的断言违规：---左括号---database_error}"
¥"Assertion violation on the database: {database_error}"
P2036
"外部连接器错误（id {id}）"
¥"Error in external connector (id {id})"
P2037
“打开了太多数据库连接：---左括号---消息}"
¥"Too many database connections opened: {message}"
Prisma Migrate（架构引擎）
¥Prisma Migrate (Schema Engine)
P3000
“创建数据库失败：---左括号---database_error}"
¥"Failed to create database: {database_error}"
P3001
“迁移可能会带来破坏性的变化并可能导致数据丢失：{migration_engine_destroy_details}"
¥"Migration possible with destructive changes and possible data loss: {migration_engine_destructive_details}"
P3002
“尝试的迁移被回滚：---左括号---database_error}"
¥"The attempted migration was rolled back: {database_error}"
P3003
“迁移的格式已更改，保存的迁移不再有效。要解决此问题，请按照以下步骤操作：https://pris.ly/d/migrate"
¥"The format of migrations changed, the saved migrations are no longer valid. To solve this problem, please follow the steps at: https://pris.ly/d/migrate"
P3004
“{database_name} 数据库是系统数据库，不应使用 prisma migrate 更改它。请连接到另一个数据库。”
¥"The {database_name} database is a system database, it should not be altered with prisma migrate. Please connect to another database."
P3005
“数据库模式不为空。详细了解如何为现有生产数据库建立基线：https://pris.ly/d/migrate-baseline"
¥"The database schema is not empty. Read more about how to baseline an existing production database: https://pris.ly/d/migrate-baseline"
P3006
“迁移 {migration_name} 未能完全应用于影子数据库。
{error_code}错误：
{inner_error}"
¥"Migration {migration_name} failed to apply cleanly to the shadow database.
{error_code}Error:
{inner_error}"
P3007
“模式引擎中尚未允许某些请求的预览功能。在使用迁移之前，请从你的数据模型中删除它们。（被阻止：{list_of_blocked_features}）”
¥"Some of the requested preview features are not yet allowed in schema engine. Please remove them from your data model before using migrations. (blocked: {list_of_blocked_features})"
P3008
“迁移 {migration_name} 已在数据库中记录为已应用。”
¥"The migration {migration_name} is already recorded as applied in the database."
P3009
“migrate 在目标数据库中发现失败的迁移，将不会应用新的迁移。详细了解如何解决生产数据库中的迁移问题：https://pris.ly/d/migrate-resolve
---左括号---详细信息}"
¥"migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
{details}"
P3010
“迁移的名称太长了。它不得超过 200 个字符（字节）。”
¥"The name of the migration is too long. It must not be longer than 200 characters (bytes)."
P3011
“迁移 {migration_name} 无法回滚，因为它从未应用到数据库。暗示：你是否传递了整个迁移名称？（例如："20201207184859_initial_migration"）”
¥"Migration {migration_name} cannot be rolled back because it was never applied to the database. Hint: did you pass in the whole migration name? (example: "20201207184859_initial_migration")"
P3012
“迁移 {migration_name} 无法回滚，因为它未处于失败状态。”
¥"Migration {migration_name} cannot be rolled back because it is not in a failed state."
P3013
“迁移中不再支持数据源提供程序数组。请更改你的数据源以使用单个提供商。阅读更多内容，请访问 https://pris.ly/multi-provider-deprecation"
¥"Datasource provider arrays are no longer supported in migrate. Please change your datasource to use a single provider. Read more at https://pris.ly/multi-provider-deprecation"
P3014
“Prisma Migrate 无法创建影子数据库。请确保数据库用户有创建数据库的权限。在 https://pris.ly/d/migrate-shadow 阅读有关影子数据库（和解决方法）的更多信息。
¥"Prisma Migrate could not create the shadow database. Please make sure the database user has permission to create databases. Read more about the shadow database (and workarounds) at https://pris.ly/d/migrate-shadow.
原始错误：{error_code}
{inner_error}"
¥Original error: {error_code}
{inner_error}"
P3015
“在 {migration_file_path} 处找不到迁移文件。请删除该目录或恢复迁移文件。”
¥"Could not find the migration file at {migration_file_path}. Please delete the directory or restore the migration file."
P3016
“数据库重置的后备方法失败，这意味着 Migrate 无法完全清理数据库。原始错误：{error_code}
{inner_error}"
¥"The fallback method for database resets failed, meaning Migrate could not clean up the database entirely. Original error: {error_code}
{inner_error}"
P3017
“找不到迁移 {migration_name}。请确保迁移存在，并且包含目录的完整名称。（例如："20201207184859_initial_migration"）”
¥"The migration {migration_name} could not be found. Please make sure that the migration exists, and that you included the whole name of the directory. (example: "20201207184859_initial_migration")"
P3018
“迁移申请失败。在错误恢复之前无法应用新的迁移。详细了解如何解决生产数据库中的迁移问题：https://pris.ly/d/migrate-resolve
迁移名称：{migration_name}
数据库错误代码：{database_error_code}
数据库错误:
{database_error} "
¥"A migration failed to apply. New migrations cannot be applied before the error is recovered from. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
Migration name: {migration_name}
Database error code: {database_error_code}
Database error:
{database_error} "
P3019
“你的架构中指定的数据源提供程序 {provider} 与 migration_lock.toml 中指定的数据源提供程序 {expected_provider} 不匹配。请删除当前的迁移目录并使用 prisma migrate dev 开始新的迁移历史记录。阅读更多：https://pris.ly/d/migrate-provider-switch"
¥"The datasource provider {provider} specified in your schema does not match the one specified in the migration_lock.toml, {expected_provider}. Please remove your current migration directory and start a new migration history with prisma migrate dev. Read more: https://pris.ly/d/migrate-provider-switch"
P3020
“Azure SQL 上禁用了影子数据库的自动创建。请使用 shadowDatabaseUrl 数据源属性设置影子数据库。
阅读文档页面以获取更多详细信息：https://pris.ly/d/migrate-shadow"
¥"The automatic creation of shadow databases is disabled on Azure SQL. Please set up a shadow database using the shadowDatabaseUrl datasource attribute.
Read the docs page for more details: https://pris.ly/d/migrate-shadow"
P3021
“无法在此数据库上创建外键。了解更多如何处理此问题：https://pris.ly/d/migrate-no-foreign-keys"
¥"Foreign keys cannot be created on this database. Learn more how to handle this: https://pris.ly/d/migrate-no-foreign-keys"
P3022
“此数据库禁用直接执行 DDL（数据定义语言）SQL 语句。请在此处阅读有关如何处理此问题的更多信息：https://pris.ly/d/migrate-no-direct-ddl"
¥"Direct execution of DDL (Data Definition Language) SQL statements is disabled on this database. Please read more here about how to handle this: https://pris.ly/d/migrate-no-direct-ddl"
prisma db pull
P4000
“自省操作无法生成架构文件：---左撑---内省错误}"
¥"Introspection operation failed to produce a schema file: {introspection_error}"
P4001
"内省的数据库是空的。"
¥"The introspected database was empty."
P4002
“内省数据库的架构不一致：---左括号---解释}"
¥"The schema of the introspected database was inconsistent: {explanation}"
Prisma 加速
¥Prisma Accelerate
除 P5011 外，与 Prisma Accelerate 相关的错误以 P6xxx 开头。
¥Prisma Accelerate-related errors start with P6xxx except for P5011.
P6000(ServerError)
捕获所有其他错误的通用错误。
¥Generic error to catch all other errors.
P6001(InvalidDataSource)
URL 格式错误；例如，它不使用 prisma:// 协议。
¥The URL is malformed; for instance, it does not use the prisma:// protocol.
P6002(Unauthorized)
连接字符串中的 API 密钥无效。
¥The API Key in the connection string is invalid.
P6003(PlanLimitReached)
已超出当前计划包含的使用量。这只能发生在 免费计划 上。
¥The included usage of the current plan has been exceeded. This can only occur on the free plan.
P6004(QueryTimeout)
已超过加速的全局超时。你可以找到极限 此处。
¥The global timeout of Accelerate has been exceeded. You can find the limit here.
另请参阅 故障排除指南 了解更多信息。
¥Also see the troubleshooting guide for more information.
P6005(InvalidParameters)
用户提供了无效的参数。目前仅与事务方式相关。例如，设置太高的超时。你可以找到极限 此处。
¥The user supplied invalid parameters. Currently only relevant for transaction methods. For example, setting a timeout that is too high. You can find the limit here.
P6006(VersionNotSupported)
所选的 Prisma 版本与 Accelerate 不兼容。当用户使用我们偶尔修剪的不稳定开发版本时，可能会发生这种情况。
¥The chosen Prisma version is not compatible with Accelerate. This may occur when a user uses an unstable development version that we occasionally prune.
P6008(ConnectionError|EngineStartError)
发动机无法启动。例如，它无法建立与数据库的连接。
¥The engine failed to start. For example, it couldn't establish a connection to the database.
另请参阅 故障排除指南 了解更多信息。
¥Also see the troubleshooting guide for more information.
P6009(ResponseSizeLimitExceeded)
已超出 Accelerate 的全局响应大小限制。你可以找到极限 此处。
¥The global response size limit of Accelerate has been exceeded. You can find the limit here.
另请参阅 故障排除指南 了解更多信息。
¥Also see the troubleshooting guide for more information.
P6010(ProjectDisabledError)
你的加速项目已被禁用。请再次 enable 才能使用。
¥Your accelerate project is disabled. Please enable it again to use it.
P5011(Too Many Requests)
此错误表示请求量超出。实现退避策略并稍后再试。如需预期高工作负载的帮助，请联系 support。
¥This error indicates that the request volume exceeded. Implement a back-off strategy and try again later. For assistance with expected high workloads, contact support.