Markdown and editors soft-wrap on their own, so the manual ~75-char line breaks across the docs added nothing but noise. Join wrapped prose, list items, and paragraphs into single lines across 67 docs — README, CLAUDE.md, deployment, usage, the RAG knowledge base, and the agent role prompts. Whitespace-only: code fences, tables, and blockquote alerts are byte-identical and the change is token-verified (no content altered). Applied with a deterministic reflow tool (committed separately). Also lands two doc edits that were awaiting commit: the measured under-load resource numbers in usage.md and the pr_reviewer additions to the org-structure RAG doc.
3.6 KiB
Task Error Troubleshooting
Cannot Claim Task
Error: "Task cannot be claimed"
Causes:
- Task not in claimable status for your role
- Task already assigned to someone else
- Wrong role for this task type
Solutions:
- Check what's actionable for you:
give_me_work()(ortriage()for PMs) - Verify your role can claim from the task's current status
- Contact PM if task needs reassignment
Claimable Status by Role:
| Role | Can Claim From | Verb |
|---|---|---|
| Developer | pending, needs_revision | i_will_work_on(task_id) |
| QA | awaiting_qa | claim_review(task_id) |
| Documenter | pending, awaiting_documentation | claim_doc_task(task_id) |
| Cell PM / Main PM | pending | i_will_plan(task_id) |
Cannot Start Task
Error: "Cannot transition to in_progress"
Causes:
- Task not claimed by you
- Task in wrong status
Solutions:
- Claim + start in one step:
i_will_work_on(task_id, plan="...")(devs),claim_review(task_id)(QA),claim_doc_task(task_id)(doc), ori_will_plan(task_id, plan, approach)(PMs) - Check current status
Note: Git branches are auto-created on claim, no waiting needed.
Cannot Submit for QA
Error: "Invalid transition from current status"
Causes:
- Task not in
in_progressorverifying - Missing required fields
Solutions:
- Move through verification first
- Ensure task is actively being worked
Self-Review Prevented
Error: "Cannot review own work" or "SELF_REVIEW_NOT_ALLOWED"
Cause: QA trying to claim, pass, or fail a task they originally developed
Solution: Another QA must handle this task. Self-review prevention applies to:
- Claiming the task (
claim_review) - Passing QA (
pass) - Failing QA (
fail)
Cannot Escalate Subtask to CEO
Error: "Cannot escalate subtask to CEO - only parent tasks can be escalated"
Cause: Attempting to escalate a task that has a parent_task_id
Solution: Escalate the parent task instead. Find the parent task ID (it's on the subtask's parent_task_id field, surfaced in your give_me_work() / triage() envelope), then escalate the parent:
escalate_to_ceo(task_id=parent_id, reason="...")
escalate_to_ceo is Main PM / Board only; Cell PMs and cell members use escalate_up(task_id, reason) instead.
Git Task: Parent Branch Required
Error: "Parent task must be claimed first to create its branch"
Cause: Trying to claim a subtask when parent task hasn't been claimed yet
Solution: Parent task must be claimed first. Branches are auto-created hierarchically:
- Parent is claimed → parent branch created
- Then subtask can be claimed → subtask branch created (forked from parent)
Task Has Incomplete Subtasks
Error: "Cannot complete task - subtasks not finished" with list of task IDs
Cause: Trying to complete a parent task while subtasks are still in progress
Solution: The error message includes which subtask IDs are blocking. Either:
- Complete the blocking subtasks first (drive them through QA → docs →
complete(task_id, notes)) - Cancel them if no longer needed (PM/CEO only — cancellation is not an agent verb; ask your PM)
Invalid Task Status for Operation
Error: "Task is in [status], expected [expected_status]"
Cause: Attempting an operation that's not valid for the current task state
Solution: Check the task's current status and follow the correct workflow:
- QA operations require
awaiting_qastatus - Documentation operations require
awaiting_documentationstatus - PM completion requires
awaiting_pm_reviewstatus