Answer: Publish returns these error codes in the code field of a diagnostic: YAML_PARSE_ERROR, UNKNOWN_CAPABILITY / UNKNOWN_SETTING, DECISION_NOT_ALLOWED, BINARY_CAPABILITY_SCOPED, FIELD_NOT_A_STRING_LIST, WHEN_PARSE_ERROR, UNKNOWN_GROUP / UNKNOWN_USER, POLICY_BOUNDARY_VIOLATION, and SETTING_REQUIREMENT_MISSING. To fix them, correct the underlying cause (e.g., valid YAML, correct capability/setting names, proper match list syntax, quoted when values, correct names/IDs, and settings that satisfy model_use rules), and check the spelling of every optional field before you publish. Status: Confirmed Entry: tool/kiro/troubleshooting/kgl-common-errors Revision: 3 Digest: sha256:d268c52d8c6683fd (changes whenever the content changes) Timeline: Created: 2026-11-16T13:08:44Z Last changed: 2026-11-20T13:25:52Z (POLICY_BOUNDARY_VIOLATION cause: — → default_model is not allowed by a model_use rule.) Last verified: 2026-11-20T13:25:52Z Next check: 2026-11-21T13:25:52Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of error codes | YAML_PARSE_ERROR | [1] | 2026-11-20 YAML_PARSE_ERROR cause | The file is not valid YAML. | [1] | 2026-11-20 UNKNOWN_CAPABILITY / UNKNOWN_SETTING cause | A typo in a capability or setting name. | [1] | 2026-11-20 DECISION_NOT_ALLOWED cause | ask on a capability that cannot ask. | [1] | 2026-11-20 BINARY_CAPABILITY_SCOPED cause | match on a capability that takes nothing. | [1] | 2026-11-20 FIELD_NOT_A_STRING_LIST cause | match: "x" in place of match: ["x"] . | [1] | 2026-11-20 WHEN_PARSE_ERROR cause | Bad when syntax, or the value is not quoted. | [1] | 2026-11-20 POLICY_BOUNDARY_VIOLATION cause | default_model is not allowed by a model_use rule. | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "KGL reference - Enterprise Management - Enterprise - Docs - Kiro". https://kiro.dev/docs/enterprise/enterprise-management/kgl/ Role: primary. Accessed: 2026-11-20T13:25:52Z Quote: "Publish returns these codes. The API returns them in the code field of a diagnostic; see EnterpriseManagementDiagnostic . Code Cause YAML_PARSE_ERROR" (Supports: error codes) Quote: "YAML_PARSE_ERROR The file is not valid YAML." (Supports: YAML_PARSE_ERROR cause) Quote: "UNKNOWN_CAPABILITY / UNKNOWN_SETTING A typo in a capability or setting name." (Supports: UNKNOWN_CAPABILITY / UNKNOWN_SETTING cause) Quote: "DECISION_NOT_ALLOWED ask on a capability that cannot ask." (Supports: DECISION_NOT_ALLOWED cause) Quote: "BINARY_CAPABILITY_SCOPED match on a capability that takes nothing." (Supports: BINARY_CAPABILITY_SCOPED cause) Quote: "FIELD_NOT_A_STRING_LIST match: "x" in place of match: ["x"] ." (Supports: FIELD_NOT_A_STRING_LIST cause) Quote: "WHEN_PARSE_ERROR Bad when syntax, or the value is not quoted." (Supports: WHEN_PARSE_ERROR cause) Quote: "POLICY_BOUNDARY_VIOLATION default_model is not allowed by a model_use rule." (Supports: POLICY_BOUNDARY_VIOLATION cause) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 73730c90b40ff4d031ecc19d51c751d6bd8225fa73676d7bea7572c7f45c0d02 (captured 2026-11-20T13:25:47Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:25:52Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:25:52Z Last attempt: 2026-11-20T13:25:52Z Notes and limitations: Extracted automatically from a single official source (section "Common errors"). Related: https://latestn.com/tool/kiro/troubleshooting/kirocrew-command-not-found How do I fix the kirocrew: command not found error after installing Kiro Crew? https://latestn.com/tool/kiro/troubleshooting/manifest-validation-rules What validation rules apply to a Kiro Crew app manifest? https://latestn.com/tool/kiro/troubleshooting/mcp-tools-not-working How do I fix MCP tools not working in Kiro Crew? https://latestn.com/tool/kiro/troubleshooting/hook-shell-command-errors How do I fix shell command errors in Kiro hooks? https://latestn.com/tool/kiro/troubleshooting/important-migration-changes What important changes should I know about when upgrading from Q CLI to Kiro CLI? https://latestn.com/tool/kiro/troubleshooting/inspect-failed-cron-run How do I inspect a failed cron run in Kiro Crew? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:25:52Z | changed | POLICY_BOUNDARY_VIOLATION cause: — → default_model is not allowed by a model_use rule. | [1] 2026-11-20T13:25:52Z | changed | WHEN_PARSE_ERROR cause: — → Bad when syntax, or the value is not quoted. | [1] 2026-11-20T13:25:52Z | changed | FIELD_NOT_A_STRING_LIST cause: — → match: "x" in place of match: ["x"] . | [1] 2026-11-20T13:25:52Z | changed | BINARY_CAPABILITY_SCOPED cause: — → match on a capability that takes nothing. | [1] 2026-11-20T13:25:52Z | changed | DECISION_NOT_ALLOWED cause: — → ask on a capability that cannot ask. | [1] 2026-11-20T13:25:52Z | changed | UNKNOWN_CAPABILITY / UNKNOWN_SETTING cause: — → A typo in a capability or setting name. | [1] 2026-11-20T13:25:52Z | changed | YAML_PARSE_ERROR cause: — → The file is not valid YAML. | [1] 2026-11-20T13:25:52Z | changed | error codes: — → YAML_PARSE_ERROR | [1] 2026-11-20T13:25:52Z | changed | POLICY_BOUNDARY_VIOLATION: default_model is not allowed by a model_use rule. → — | [1] 2026-11-20T13:25:52Z | changed | UNKNOWN_GROUP / UNKNOWN_USER: A name or a wrong ID in when . → — | [1] 2026-11-20T13:25:52Z | changed | WHEN_PARSE_ERROR: Bad when syntax, or the value is not quoted. → — | [1] 2026-11-20T13:25:52Z | changed | FIELD_NOT_A_STRING_LIST: match: "x" in place of match: ["x"] . → — | [1] 2026-11-20T13:25:52Z | changed | BINARY_CAPABILITY_SCOPED: match on a capability that takes nothing. → — | [1] 2026-11-20T13:25:52Z | changed | DECISION_NOT_ALLOWED: ask on a capability that cannot ask. → — | [1] 2026-11-20T13:25:52Z | changed | UNKNOWN_CAPABILITY / UNKNOWN_SETTING: A typo in a capability or setting name. → — | [1] 2026-11-20T13:25:52Z | changed | YAML_PARSE_ERROR: The file is not valid YAML. → — | [1] 2026-11-19T13:18:01Z | recovered | Check succeeded again | — 2026-11-19T13:18:01Z | changed | POLICY_BOUNDARY_VIOLATION: — → default_model is not allowed by a model_use rule. | [1] 2026-11-19T13:18:01Z | changed | UNKNOWN_GROUP / UNKNOWN_USER: — → A name or a wrong ID in when . | [1] 2026-11-19T13:18:01Z | changed | WHEN_PARSE_ERROR: — → Bad when syntax, or the value is not quoted. | [1] 2026-11-19T13:18:01Z | changed | FIELD_NOT_A_STRING_LIST: — → match: "x" in place of match: ["x"] . | [1] 2026-11-19T13:18:01Z | changed | BINARY_CAPABILITY_SCOPED: — → match on a capability that takes nothing. | [1] 2026-11-19T13:18:01Z | changed | DECISION_NOT_ALLOWED: — → ask on a capability that cannot ask. | [1] 2026-11-19T13:18:01Z | changed | UNKNOWN_CAPABILITY / UNKNOWN_SETTING: — → A typo in a capability or setting name. | [1] 2026-11-19T13:18:01Z | changed | YAML_PARSE_ERROR: — → The file is not valid YAML. | [1] 2026-11-19T13:18:01Z | changed | POLICY_BOUNDARY_VIOLATION cause: default_model is not allowed by a model_use rule. → — | [1] 2026-11-19T13:18:01Z | changed | UNKNOWN_GROUP / UNKNOWN_USER cause: A name or a wrong ID in when . → — | [1] 2026-11-19T13:18:01Z | changed | WHEN_PARSE_ERROR cause: Bad when syntax, or the value is not quoted. → — | [1] 2026-11-19T13:18:01Z | changed | FIELD_NOT_A_STRING_LIST cause: match: "x" in place of match: ["x"] . → — | [1] 2026-11-19T13:18:01Z | changed | BINARY_CAPABILITY_SCOPED cause: match on a capability that takes nothing. → — | [1] 2026-11-19T13:18:01Z | changed | DECISION_NOT_ALLOWED cause: ask on a capability that cannot ask. → — | [1] 2026-11-19T13:18:01Z | changed | UNKNOWN_CAPABILITY / UNKNOWN_SETTING cause: A typo in a capability or setting name. → — | [1] 2026-11-19T13:18:01Z | changed | YAML_PARSE_ERROR cause: The file is not valid YAML. → — | [1] 2026-11-18T13:21:21Z | check-failed | Extraction did not pass verification: answer must be 10 to 800 characters | — 2026-11-16T13:08:44Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/kgl-common-errors/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/troubleshooting/kgl-common-errors POST: https://latestn.com/dispute/tool/kiro/troubleshooting/kgl-common-errors with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/kgl-common-errors?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are common KGL errors in Kiro and how do I fix them? Revision 3, last verified 2026-11-20T13:25:52Z. https://latestn.com/tool/kiro/troubleshooting/kgl-common-errors (accessed 2026-11-21T09:59:50Z). @misc{LatestN_tool_kiro_troubleshooting_kgl_common_errors_r3, title = {What are common KGL errors in Kiro and how do I fix them?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/kgl-common-errors}}, note = {Revision 3; digest sha256:d268c52d8c6683fd; last verified 2026-11-20T13:25:52Z; accessed 2026-11-21T09:59:50Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/troubleshooting/kgl-common-errors