FoundationAgents/OpenManus · error · ToolError
Invalid step_status: {step_status}. Valid statuses are: not_
Error message
Invalid step_status: {step_status}. Valid statuses are: not_started, in_progress, completed, blocked What it means
Error "Invalid step_status: {step_status}. Valid statuses are: not_started, in_progress, completed, blocked" thrown in FoundationAgents/OpenManus.
Source
Thrown at app/tool/planning.py:292
raise ToolError(f"No plan found with ID: {plan_id}")
if step_index is None:
raise ToolError("Parameter `step_index` is required for command: mark_step")
plan = self.plans[plan_id]
if step_index < 0 or step_index >= len(plan["steps"]):
raise ToolError(
f"Invalid step_index: {step_index}. Valid indices range from 0 to {len(plan['steps'])-1}."
)
if step_status and step_status not in [
"not_started",
"in_progress",
"completed",
"blocked",
]:
raise ToolError(
f"Invalid step_status: {step_status}. Valid statuses are: not_started, in_progress, completed, blocked"
)
if step_status:
plan["step_statuses"][step_index] = step_status
if step_notes:
plan["step_notes"][step_index] = step_notes
return ToolResult(
output=f"Step {step_index} updated in plan '{plan_id}'.\n\n{self._format_plan(plan)}"
)
def _delete_plan(self, plan_id: Optional[str]) -> ToolResult:
"""Delete a plan."""
if not plan_id:
raise ToolError("Parameter `plan_id` is required for command: delete")
View on GitHub (pinned to 52a13f2a57)
Solutions
- Set `step_status` to one of: not_started, in_progress, completed, blocked.
- Omit `step_status` entirely if you only want to update step_notes.
When it happens
Trigger: Raised when `mark_step` is called with a `step_status` value outside the allowed set: not_started, in_progress, completed, blocked.
Common situations: See trigger scenarios.
AI-assisted analysis of FoundationAgents/OpenManus@52a13f2a57 (2026-08-15).
Data as JSON: /api/errors/0566ed725a301f78.
Report an issue: GitHub.