本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。

# 由于配置错误，作业停留在 `RUNNABL` E 中
<a name="sm_job_stuck_in_runnable_misconfiguration"></a>

**已超过服务环境资源上限**  
当提交给 AWS Batch via 的任务`SubmitServiceJob`到达队列的最前端，并且它需要的实例数超过所连接的服务环境的容量限制时， AWS Batch 将推断出由于超出服务环境容量限制而导致配置错误。服务环境`capacityLimits`结构支持不同的`capacityUnit`值，具体取决于在作业队列上配置的调度算法。      
[See the AWS documentation website for more details](http://docs.aws.amazon.com/zh_cn/batch/latest/userguide/sm_job_stuck_in_runnable_misconfiguration.html)
+ **作业卡住时的 `statusReason` 消息：**`MISCONFIGURATION:SERVICE_ENVIRONMENT_MAX_RESOURCE - Service environment(s) associated with the job queue cannot meet the capacity requirement of the job.`
+ **用于 `jobStateTimeLimitActions` 的 `reason`：**`MISCONFIGURATION:SERVICE_ENVIRONMENT_MAX_RESOURCE`
+ **`statusReason`任务终止后的消息`jobStateTimeLimitActions`：**`Terminated by JobStateTimeLimit action due to reason: MISCONFIGURATION:SERVICE_ENVIRONMENT_MAX_RESOURCE`

**已超过配额份额限制**  
当提交给 AWS Batch via 的任务`SubmitServiceJob`到达队列的最前端，并且它需要的实例数超过配额份额的容量限制时， AWS Batch 将推断出由于超出配额共享容量限制而导致配置错误。此分析取决于配额份额的配置方式。      
[See the AWS documentation website for more details](http://docs.aws.amazon.com/zh_cn/batch/latest/userguide/sm_job_stuck_in_runnable_misconfiguration.html)
+ **用于 `jobStateTimeLimitActions` 的 `reason`：**`MISCONFIGURATION:QUOTA_MANAGEMENT_LIMIT_EXCEEDED`
+ **`statusReason`任务终止后的消息`jobStateTimeLimitActions`：**`Terminated by JobStateTimeLimit action due to reason: MISCONFIGURATION:QUOTA_MANAGEMENT_LIMIT_EXCEEDED`