Open
Conversation
Removed 28 unused error codes from docs to match source: UUIDV7: 003, 005, 010, 011, 012 API: 001, 002 AGENT: 001 PROFILE: 001, 002 TOOL: 001, 002, 003, 004, 006 GATE: 004 STARTUP: 006 SANDBOX: 001, 002, 003 EXEC: 004, 005, 006, 007, 008, 010, 011 CRED: 002 Result: 71 documented error codes remain Docs now 100% synchronized with usezombie source
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
179
to
186
| |---|---|---|---| | ||
| | `UZ-EXEC-001` | 500 | Execution session create failed | Execution session creation failed. Check runner availability. | | ||
| | `UZ-EXEC-002` | 500 | Stage start failed | Stage failed to start. Check runner configuration. | | ||
| | `UZ-EXEC-003` | 500 | Execution timeout kill | Execution exceeded the timeout limit and was killed. | | ||
| | `UZ-EXEC-004` | 500 | Execution OOM kill | Execution exceeded memory limit and was killed. | | ||
| | `UZ-EXEC-005` | 500 | Execution resource kill | Execution exceeded resource limits and was killed. | | ||
| | `UZ-EXEC-006` | 500 | Execution transport loss | Connection to execution transport was lost. | | ||
| | `UZ-EXEC-007` | 500 | Execution lease expired | Execution lease expired. The task took too long to complete. | | ||
| | `UZ-EXEC-008` | 403 | Execution policy deny | Execution was denied by policy. Check firewall rules. | | ||
| | `UZ-EXEC-009` | 500 | Execution startup posture failure | Execution startup posture check failed. Verify runner security config. | | ||
| | `UZ-EXEC-010` | 500 | Execution crash | The execution process crashed. Check logs for details. | | ||
| | `UZ-EXEC-011` | 403 | Landlock policy deny | Landlock policy denied the filesystem operation. | | ||
| | `UZ-EXEC-012` | 500 | Runner agent init failed | Runner agent initialization failed. Check configuration. | | ||
| | `UZ-EXEC-013` | 500 | Runner agent run failed | Runner agent execution failed. Check logs for details. | | ||
| | `UZ-EXEC-014` | 400 | Runner invalid config | Runner configuration is invalid. Check config_json fields. | |
There was a problem hiding this comment.
operator/observability/error-codes.mdx still documents every code this PR removes — UZ-EXEC-004 through UZ-EXEC-011, UZ-CRED-002, and UZ-SANDBOX-001 — with detailed operator remediation steps. Since this PR claims those codes were deleted from the source, the operator page is now stale and will give wrong guidance to anyone who encounters one of those codes in logs. The same codes are also referenced inline in operator/security/sandbox.mdx (lines 87–89) and operator/security/model.mdx (lines 39–40).
Prompt To Fix With AI
This is a comment left during a code review.
Path: api-reference/error-codes.mdx
Line: 179-186
Comment:
**Operator error-codes page not updated in sync**
`operator/observability/error-codes.mdx` still documents every code this PR removes — `UZ-EXEC-004` through `UZ-EXEC-011`, `UZ-CRED-002`, and `UZ-SANDBOX-001` — with detailed operator remediation steps. Since this PR claims those codes were deleted from the source, the operator page is now stale and will give wrong guidance to anyone who encounters one of those codes in logs. The same codes are also referenced inline in `operator/security/sandbox.mdx` (lines 87–89) and `operator/security/model.mdx` (lines 39–40).
How can I resolve this? If you propose a fix, please make it concise.| | `UZ-EXEC-006` | 500 | Execution transport loss | Connection to execution transport was lost. | | ||
| | `UZ-EXEC-007` | 500 | Execution lease expired | Execution lease expired. The task took too long to complete. | | ||
| | `UZ-EXEC-008` | 403 | Execution policy deny | Execution was denied by policy. Check firewall rules. | | ||
| | `UZ-EXEC-009` | 500 | Execution startup posture failure | Execution startup posture check failed. Verify runner security config. | |
There was a problem hiding this comment.
UZ-EXEC-009 description conflicts between pages
This page (synced with source) describes UZ-EXEC-009 as "Execution startup posture failure", but operator/observability/error-codes.mdx line 24 describes the same code as "OOM killed" (EXECUTOR_MEMORY_LIMIT_MB exceeded). The two meanings are contradictory — an operator hitting this code will get the wrong remediation advice from the operator reference page.
Prompt To Fix With AI
This is a comment left during a code review.
Path: api-reference/error-codes.mdx
Line: 183
Comment:
**`UZ-EXEC-009` description conflicts between pages**
This page (synced with source) describes `UZ-EXEC-009` as **"Execution startup posture failure"**, but `operator/observability/error-codes.mdx` line 24 describes the same code as **"OOM killed"** (`EXECUTOR_MEMORY_LIMIT_MB` exceeded). The two meanings are contradictory — an operator hitting this code will get the wrong remediation advice from the operator reference page.
How can I resolve this? If you propose a fix, please make it concise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Synchronizes api-reference/error-codes.mdx with the usezombie source code after cleanup of unused error codes.
Changes
Removed 28 unused error codes from documentation:
Result
Verification
All remaining codes exist in usezombie source and are actively used.
Greptile Summary
This PR removes 28 error codes from
api-reference/error-codes.mdxto match a source-side cleanup in usezombie PR #207, reducing the documented set from 99 to 71 codes. The arithmetic is correct and the remaining table entries are well-formed, but the sync is incomplete.operator/observability/error-codes.mdxstill documents all the removed codes (UZ-EXEC-004–UZ-EXEC-011,UZ-CRED-002,UZ-SANDBOX-001) with operator remediation guidance, andoperator/security/sandbox.mdx/operator/security/model.mdxcontain inline references to several of them.UZ-EXEC-009has contradictory descriptions across pages: "Execution startup posture failure" here vs. "OOM killed" in the operator reference.Confidence Score: 3/5
Safe to merge for the API reference page itself, but the companion operator docs pages were not updated and now contain stale or contradictory information.
Two P1 findings: the operator error-codes page and two security pages still reference removed codes, and UZ-EXEC-009 has a contradictory description between pages. These are documentation correctness issues that could send operators down the wrong remediation path.
operator/observability/error-codes.mdx, operator/security/sandbox.mdx, operator/security/model.mdx
Important Files Changed
operator/observability/error-codes.mdxand two security pages were not updated and still reference several of the removed codes.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD src["usezombie source\n(PR #207 cleanup)"] apiref["api-reference/error-codes.mdx\n✅ updated (71 codes)"] opref["operator/observability/error-codes.mdx\n❌ not updated (still has\nEXEC-004–011, CRED-002, SANDBOX-001)"] sandbox["operator/security/sandbox.mdx\n❌ references EXEC-008, EXEC-010, EXEC-011"] model["operator/security/model.mdx\n❌ references SANDBOX-001"] posthog["operator/observability/posthog-events.mdx\n⚠️ references UZ-SANDBOX-*"] src -->|synced| apiref src -.->|not synced| opref src -.->|not synced| sandbox src -.->|not synced| model src -.->|not synced| posthogPrompt To Fix All With AI
Reviews (1): Last reviewed commit: "docs: sync error-codes.mdx with source c..." | Re-trigger Greptile